@GrahamcOfBorg build python310.pkgs.setuptools
@GrahamcOfBorg build python310Packages.pip

tests fail due to python310 not being able to install from a wheel.

I think this this commit is pretty uncontroversial, and it will make future updates easier

#100389 will remain open until the python ecosystem can install wheels

Are you watching my screen?! I was just looking again into this and the upstream CPython issue :-)

This doesn't work on macOS: https://hydra.nixos.org/job/nixpkgs/trunk/python310.x86_64-darwin/all

Unfortunately if you try to install python3 on macOS it tries to install this now, rather than python3-3.9.0 which works.

python3 should still point to python38 ....

unless you have an overlay. But that's not nixpkgs, that's your local machine at that point.

Yes, nix-env --install --attr nixpkgs.python3 installs python38, but nix-env install python3 installs python3-3.10.0a1. Also nix-env -u will try to upgrade both python3-3.9.0 and python3-3.8.6 to python3-3.10.0a1.

oh.... nix-env....

python310 isn't really meant to be used... and can't even install wheels atm due to upstream issues.

also, I don't have mac hardware, so a darwin contributor will need to contribute a working darwin build. I can mark this as a linux only to avoid it failing to build. But now that ofborg doesn't build darwin builds, the only "feedback" is hydra. And even then that's a particularly slow iteration loop

If it's not meant to be used, it's probably an issue that affects Linux as well, on distributions other than nixos: if I run nix-env --install python3 on ubuntu I'll also get python3-3.10.0a1, and it sounds like even though it builds correctly, it doesn't function correctly.

personally, I don't use nix-env for this case, and many others.....

for python, or any tool really, you should always pin something "up until" the next breaking change. python has breaking changes between minor versions, so getting the latest isn't what you want.

Really the issue is with nix-env's trying to imply desired behavior.

Yeah nix-shell with a derivation for a reproducible development environment makes more sense than nix-env, maybe there's a some packages that aren't meant to be used with nix-env.

I view nix-env as, "similar to other package managers", but misses the mark on why nix is great. Almost to the point that people should avoid using it for package installation.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/new-users-using-nix-not-nixos-wrong/9996/1

@uri-canva the first thing to learn about nix-env is, don't ever use nix-env -i, but always nix-env -iA.