Could not find suitable distribution for Requirement.parse('pytest-runner<3dev,>=2.0')

You will need to patch the source to allow a more recent version of pytest-runner.

I updated the expression, but the tests now triggers a bug in the way python3 is build at the moment.

On an older NixOS system:

$ python3 -c 'import sysconfig; print(sysconfig.get_config_var("INCLUDEPY"))' 
/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/include/python3.6m

On the current unstable channel:

$ nix-shell --pure -p python36 --run "python3 -c 'import sysconfig; print(sysconfig.get_config_var(\"INCLUDEPY\"))'"
/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-python3-3.6.8/include/python3.6m

I will triage the source of the issue a bit longer, but it seems like nuke-references breaks sysconfig at the moment.

That will be fixed by #54486.

This pull request has been mentioned on Nix community. There might be relevant details there:

https://discourse.nixos.org/t/cannot-link-against-python/2054/2

So I guess we will have to wait for staging to be merged into master, before we can run these test again. Not to mention that I am still waiting to be added as a maintainer in a previous pull-request.

You can also make your PR against staging.

@dotlambda: True, that is probably the easiest.

Now with staging-next as base and the missing maintainer entry.

@GrahamcOfBorg build python2.pkgs.scikit-build python3.pkgs.scikit-build

@GrahamcOfBorg build python2.pkgs.scikit-build

I split the commit in two and added the missing spelling correction.

@FlorianFranzen Thank you for your patience!

@GrahamcOfBorg build python2.pkgs.scikit-build

@dotlambda No problem. I was the one who pushed a broken commit.

The Python 3 builds are the most important ones, as the scikit-build testsuite will tell if Python's sysconfig is working (fixed by #54486, which was merged into unstable-next).