| Age | Commit message (Collapse) | Author |
|---|
|
https://docs.python.org/3.11/whatsnew/changelog.html#python-3-11-0-release-candidate-2
|
|
Store the intermediate artifacts. In time, we should build, install and
test in separate derivations as that reduces circular dependencies,
avoids rebuilds when fixing tests, and makes it possible to use the
wheels for creating say virtualenv's.
|
|
|
|
|
|
https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html
Fixes: CVE-2020-10735
|
|
https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html
Fixes: CVE-2020-10735
|
|
https://docs.python.org/3.9/whatsnew/changelog.html#python-3-9-14-final
https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html
Fixes: CVE-2020-10735
|
|
https://docs.python.org/3.10/whatsnew/changelog.html\#python-3-10-7-final
https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html
Fixes: CVE-2020-10735
|
|
|
|
Run the installSphinxPhase earlier, so install errors are caught early,
before long and expensive test are started.
|
|
The loop variable to find the documentation source root was
unnecessarily short, rename it to something meaningful.
|
|
Improve the documentation by moving it from the hook script into the
Python section in the manual and adding code examples.
|
|
Removes the up until now unused option to specify a `sphinxOutdir` in
favor of allowing to specify multiple builders, which is for example
useful for generating both documentation and manpages using the hook.
Since the output path cannot be determined from within the package we
automatically generate it and add a diversion for manpages, so they land
in the correct output and path.
|
|
|
|
|
|
setup-hooks/separate-debug-info.sh: don't inhibit strip hook
|
|
|
|
|
|
https://docs.python.org/3.11/whatsnew/changelog.html#python-3-11-0-beta-5
|
|
|
|
Before the change separate-debug-info.sh did the stripping itself.
This scheme has a few problems:
1. Stripping happens only on ELF files. *.a and *.o files are skipped.
Derivations have to do it manually. Usually incorrectly
as they don't run $RANLIB (true for `glibc` and `musl`).
2. Stripping happens on all paths. Ideally only `stripDebugList` paths
should be considered.
3. Host strip is called on Target files.
This change offloads stripping logic to strip hook. This strips more
files for `glibc` and `musl`. Now we can remove most $STRIP calls
from individual derivations.
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
|
|
Python package sets can be overridden by overriding an interpreter
and passing in `packageOverrides = self: super: {...};`. This is fine
in case you need a single interpreter, however, it does not help you
when you want to override all sets.
With this change it is possible to override all sets at once by
appending a list of "extensions" to `pythonPackagesExtensions`.
From reading the implementation you might wonder why a list is used, and
not
`lib.composeExtensions`? The reason is the latter requires knowledge of
the library function. This approach should be easier for most users
as it is similar to how we append to lists of e.g. inputs or patches
when overriding a derivation.
|
|
https://docs.python.org/3.10/whatsnew/changelog.html#python-3-10-6-final
https://pythoninsider.blogspot.com/2022/08/python-3106-is-available.html
https://www.python.org/downloads/release/python-3106/
|
|
https://pythoninsider.blogspot.com/2022/07/python-3110b5-is-now-available.html
https://www.python.org/downloads/release/python-3110b5/
|
|
This allows importing and inspecting the build result, which is required
for the psycopg (3.x) package.
|
|
https://www.python.org/downloads/release/python-3110b4/
https://pythoninsider.blogspot.com/2022/07/python-3110b4-is-now-available.html
|
|
|
|
python applications should not propagate python in PATH but we do it
nevertheless to avoid rebuilds see https://github.com/NixOS/nixpkgs/issues/170887
for an explanation.
|
|
|
|
|
|
The PEP600 standard gives Python's naming scheme for various
architectures; it follows the convention which was in use by Fedora in
2014. According to PEP600, the architecture name for Power PC is
`ppc64le`, not `powerpc64le`. This is also how python3 declares its
"supported wheels" under Debian on PowerPC, as checked with `pip debug
--verbose`
$ pip debug --verbose | grep powerpc
$ pip debug --verbose | grep ppc | head
cp39-cp39-manylinux_2_31_ppc64le
cp39-cp39-manylinux_2_30_ppc64le
cp39-cp39-manylinux_2_29_ppc64le
cp39-cp39-manylinux_2_28_ppc64le
cp39-cp39-manylinux_2_27_ppc64le
cp39-cp39-manylinux_2_26_ppc64le
cp39-cp39-manylinux_2_25_ppc64le
cp39-cp39-manylinux_2_24_ppc64le
cp39-cp39-manylinux_2_23_ppc64le
Let's adjust the `pythonHostPlatform` expression in
cpython/default.nix to pass the architecture using the naming scheme
Python expects.
Verified on a Raptor Computing Systems Talos II. Without this commit,
PyQt5 fails to build, failing with "unsupported wheel". With this
commit, it builds successfully.
|
|
|
|
|
|
see https://github.com/NixOS/nixpkgs/pull/169475#issuecomment-1129517328
patch by adisbladis
Co-authored-by: adisbladis <adisbladis@gmail.com>
|
|
pythonRelaxDepsHook: fix usage in packages with `-` in pname
|
|
|
|
|
|
|
|
https://www.python.org/downloads/release/python-3110b2/
https://pythoninsider.blogspot.com/2022/05/python-3110b2-is-now-available.html
With updated darwin-libutil.patch provided by Randy Eckenrode.
Co-Authored-By: Randy Eckenrode <randy@largeandhighquality.com>
|
|
https://docs.python.org/release/3.10.5/whatsnew/changelog.html#python-3-10-5-final
|
|
|
|
|
|
|
|
Every package should have a maintainer and we should not throw it away if we arleady have one.
Also in reality the maintainer of python3 is also the one of python3-minimal
|
|
|
|
|
|
|
|
GCC does not come with a `libgcc_eh.a` for the target platform if
it was built without `--enable-shared`. That flag was removed with
c6dd11ca39ac87899c92b13a743f104c31cadb26, meaning we should no longer
attempt to link against that lib.
|
|
|
