02:22 <winter> Hi folks. I'm trying to figure out why, as of PyPy v7.3.6 (3.8, notably not 3.7), something with regards to PYTHONPATH(?) is causing a bootstrapped build of pip (meaning we build setuptools, wheel, and pip self-contained; see

02:22 <winter> https://github.com/NixOS/nixpkgs/blob/2d84e9d64687110e21b6867ac7a058155f6f9a9e/pkgs/development/python-modules/bootstrapped-pip/default.nix#L41-L59) is failing to build because the pip install cannot find `bdist_wheel` (even though it is in PYTHONPATH).

02:22 <winter> Is there any change between PyPy 3.7 and 3.8 that may have caused this? It does seem a bit odd, though, so I'm *assuming* it's a bug?

02:22 <winter> Thanks!

04:44 <winter> Notably, this works just fine in CPython 3.8+.

05:32 <mattip> winter: maybe the value of python.sitePackages does not take into account that the layout of directories changed

05:33 <mattip> in pypy3.7 there is a site-packages directly under the base directory,

05:33 <mattip> in pypy3.8 we moved to a more cpython-like layout and site-packages is under lib/pypy3.8

05:41 <mattip> this looks correct

05:41 <mattip> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/interpreters/python/pypy/prebuilt.nix#L36

05:41 <mattip> this looks wrong

05:41 <mattip> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/interpreters/python/pypy/default.nix#L30

05:42 <mattip> I don't know much about nix, is that how the value of python.sitePackages is set?

06:04 <winter> i think you actually hit the nail on the head :)

06:04 <winter> give me a sec

06:07 <winter> i read that changelog line and was like "maybe that's it.."

06:07 <winter> but couldn't connect the dots

06:07 <winter> (i am absolutely not a python person :)

06:12 <winter> ugh, gotta rebuild pypy... will come back to this later

06:12 <winter> you're absolutely right though

06:14 <winter> https://github.com/NixOS/nixpkgs/commit/2ced686d5b94ec67d66892257074ebe612b9292b#diff-8f347736a0dbb3d9b09a9fb887bf2669bd3b1dee79b72910e418f37ca7342e15R36

06:14 <winter> fridh changed it for prebuilt here but never changed it for the main package

06:15 <winter> mattip: got a preferred name to be credited by? else i'll just say mattip in #pypy :)

06:15 <mattip> mattip is fine, or just no accredidation is fine too

06:17 <winter> (no references anywhere other than its definition)

06:17 <winter> > They are primarily added for testing purposes and development on the non-prebuilt PyPy interpreters as it can speed up translation significantly.

06:18 <winter> hm, guess i'm reading up on the build process

06:19 <winter> ah, i see. interesting.

06:19 <mattip> typically, you would use pypy2.7 to build pypy3.x since it will be much faster

06:19 <winter> yup, looks like that's what we're doing

06:19 <winter> no clue why we define a prebuilt pypy 3.9 though

06:19 <mattip> and you need a python2.7 (either cpython or pypy) to build pypy2.7

06:20 <mattip> can't help you there :)

06:20 <winter> i'll get this building some time tomorrow, and will come back if anything happens :)

06:20 <winter> this has been broken for over a year

06:20 <winter> yet the fix has been right there the whole time

06:21 <winter> :D thanks again

07:32 <mattip> cool, thanks for fixing int

07:32 <mattip> it

12:57 <kostasGR> yo guys, do you also have discord or do we prefer to live in 1990 ?

13:03 <kostasGR> I just wanted to ask if there is a nightly build for python 3.10.6 Ubuntu

13:09 <Atque> kostasGR: Discord turns you into a corporation's slave.

13:11 <cfbolz> wow, this is a wildly off-topic discussion here

13:12 <mattip> personally, I much prefer to live in 1990s. At least then liberal democracies were winning

13:12 <mattip> for nightly builds see https://buildbot.pypy.org/nightly/py3.10/

13:20 <kostasGR> i use the last nightly build of 3.10 but I get a weird error when trying to compile orjson module with this pypy:

13:20 <kostasGR> │ exit code: 1

13:20 <kostasGR> × Preparing metadata (pyproject.toml) did not run successfully.

13:20 <kostasGR> ╰─> [6 lines of output]

13:20 <kostasGR> Checking for Rust toolchain....

13:20 <kostasGR> Cargo, the Rust package manager, is not installed or is not on PATH.

13:20 <kostasGR> This package requires Rust and Cargo to compile extensions. Install it through

13:20 <kostasGR> the system's package manager or via https://rustup.rs/

13:20 <kostasGR> [end of output]

13:20 <kostasGR> note: This error originates from a subprocess, and is likely not a problem with pip.

13:20 <kostasGR> error: metadata-generation-failed

13:20 <kostasGR> any suggestions ?

13:22 <LarstiQ> is that when building cryptography?

13:23 <Alex_Gaynor> Did you read the error message? Compiling this package requires rust be installed.

13:25 <kostasGR> it is weird cause this package is already installed in my machine (for normal python not pypy) without the above required packaqge

13:26 <Alex_Gaynor> It's likely that the package distributes a wheel -- a pre-compiled artifact -- for cpython.

13:31 <kostasGR> hmm i did install the package in my machine but still getting the same error

13:31 <kostasGR> weird

13:56 <kostasGR> i believe i will wait for the stable version of pypy for 3.10 to be out, since nightly builds are already here i doubt it will be long

14:28 <nimaje> (was probably the diffrence between build time dependencies and runtime dependencies)

14:31 <Dejan> I wish I was here to tell him that I prefer simplicity of IRC over Discord

15:15 <mattip> about early importing array: see 8f43c7212d95

15:16 <mattip> _rawffi still has this problem

20:12 <Dejan> I am impressed with 3.10 progress

20:13 <Dejan> You guys rock