-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python310Packages.buildPythonPackage: introduce pyproject option #254136
Conversation
The documentation here needs some love |
replaced all the |
* `pyproject`: Whether the pyproject format should be used. When set to `true`, | ||
`pypaBuildHook` will be used, and you can add the required build dependencies | ||
from `build-system.requires` to `nativeBuildInputs`. Note that the pyproject | ||
format falls back to using `setuptools`, so you can use `pyproject = true` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How? setuptools
is not supposed to be available by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
by that I mean pypaBuildHook
will try to use setuptools
even if pyproject.toml
doesn't exist, but it still needs to be added to nativeBuildInputs
fixed merge conflicts |
Description of changes
#253154
adds the
pyproject
option that conflicts withformat
, wherepyproject = true
is equivalent toformat = "pyproject"
, andpyproject = false
is equivalent toformat = "other"
, and 3 more commits to demonstrate the conversion offormat = "pyproject" | "setuptools" | "other"
to thepyproject
optionThings done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)