| Age | Commit message (Collapse) | Author |
|---|
|
mkPythonDerivation: apply checks to buildInputs as well
fixup: add a suggestion about nativeBuildInputs
Clean up the wording, add reasons for the suggestions
switch to throw
Adjust error to clarify build-time vs. run-time
|
|
|
|
|
|
https://hydra.nixos.org/build/215259697
This is most likely fallout from PR #209870
|
|
|
|
https://docs.python.org/release/3.11.3/whatsnew/changelog.html
|
|
https://docs.python.org/release/3.10.11/whatsnew/changelog.html
|
|
https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-0-alpha-7
|
|
|
|
https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-0-alpha-6
|
|
|
|
|
|
python3: allow enabling framework on darwin
|
|
- Prune unused imports
- Collect imports at the top
- Removed unused exception assignments
- Fill bare except clause with
- Expand overly long check_output lines
|
|
Retrieve the current package hash and use it for a more precise match,
which allows us to update a derivation in situation where multiple
hashes are present.
|
|
By settings `passthru.skipBulkUpdate = true` in a python package, it
will be excluded from bulk update runs.
This is useful in case of fragile packages, that require special
attention during updates.
|
|
Previously when packages that required the git fetcher were updated, we
would wrongly rely on `nix-prefetch-url`, which would reliable break the
hash.
Instead we need to use `nix-prefetch-git` to determine the proper hash,
when the relevant attributes are present.
|
|
pypy3{8,9}: fix sitePackages
|
|
Fixes the build after cpython switched to hash.
|
|
When PyPy introduced Python 3.8 support with version 7.3.6, they also
migrated to using CPython's directory layout [0]:
> The 3.8 package now uses the same layout as CPython, and many of the
PyPy-specific changes to `sysconfig`, `distutils.sysconfig`, and
`distutils.commands.install.py` have been removed. The stdlib now is
located in `<base>/lib/pypy3.8` on `posix` systems...
When we upgraded past this version and added Python 3.8 support [1], the
`sitePackages` value was never updated, leading `bootstrapped-pip` to fail
to build, because wheel was trying to be located in `$out/site-packages`,
when it was actually installed to `$out/lib/pypy3.8/site-packages`.
[0]: https://www.pypy.org/posts/2021/10/pypy-v736-release.html
[1]: eec28b8cfd7923a876fb47af8a0459c1a550fd97
|
|
Conflicts:
pkgs/development/libraries/pmdk/default.nix
|
|
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
|
|
|
|
|
|
|
|
|
|
Fixes: ee90eca180f ("cpython: Migrate sha256 occurences to hash")
|
|
The virtualenv mode is trying to be smart and checks whether it can
write to $out, which for some reason fails on darwin.
> virtualenv: error: argument dest: the destination . is not write-able at /nix/store
But what does work is creating it in the pwd and moving it to $out,
because mv just does what it is told.
|
|
Allow python3.tests to eval on other platforms than linux, by excluding
conda tests when not on linux, because they include alsa-lib, which is
linux-only.
|
|
|
|
https://docs.python.org/release/3.11.2/whatsnew/changelog.html
|
|
https://docs.python.org/release/3.10.10/whatsnew/changelog.html
|
|
|
|
|
|
|
|
https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-0-alpha-4
https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-0-alpha-5
|
|
|
|
|
|
|
|
python311: fix cross compilation
|
|
|
|
|
|
Previously:
nix-repl> python3.pkgs.WSME
error: WSME-0.11.0 not supported for interpreter python3.10
nix-repl> python3.pkgs.WSME.overridePythonAttrs (_: { disabled = false; })
error: WSME-0.11.0 not supported for interpreter python3.10
Now:
nix-repl> python3.pkgs.WSME
error: WSME-0.11.0 not supported for interpreter python3.10
«derivation
nix-repl> python3.pkgs.WSME.overridePythonAttrs (_: { disabled = false; })
«derivation /nix/store/cxkiwdfm146zvl573s2hahlbjd1wfrrp-python3.10-WSME-0.11.0.drv»
|
|
|
|
Previously, unless unsupported platforms were allowed, the following
would fail to evaluate (from an "x86_64-linux" system):
pkgsCross.x86_64-freebsd.__splicedPackages.docutils.__spliced.buildHost
It shouldn't have, because the buildHost package ends up being for
Linux. This broke evaluation of e.g. pkgsCross.x86_64-freebsd.libdrm,
because it has docutils in nativeBuildInputs. mkDerivation would try
to go through __spliced.buildHost on docutils to get to the Linux
version, but the check in ensurePythonModules would kick in first,
triggering the meta check because of the equality check in the
implementation of hasPythonModule, which would fail because Python is
not marked as supported on FreeBSD in Nixpkgs at the moment. Thus,
even though they're not supposed to be, the meta checks would be
triggered even though the only attribute being accessed on the
unsupported derivation was __spliced.
We can fix this by using the same mechanism used to implement the meta
checks themselves: lib.extendDerivation. Now, attempting to access
drvPath or outPath on an attribute that fails the validity check will
produce the same error as before, but other accesses will be allowed
through, fixing splicing.
I've tested evaluation of packages that pass and fail the validity
check, and confirmed that the behaviour is still correct.
|
|
It wasn't clear before, but it turns out that this is just four
separate conditions, and an attribute is valid if any of the
conditions is true, so we don't need a sea of parentheses to express
it.
|
|
|
|
|
|
|
|
python37: remove leftovers
|
