summaryrefslogtreecommitdiff
path: root/pkgs/development/interpreters/python
AgeCommit message (Collapse)Author
2020-03-03python: add pythonRemoveTestsDirHookJonathan Ringer
This will automatically remove a top-level "tests" directory from being installed.
2020-03-03python39: 3.9.0.a3 -> 3.9.0.a4Jonathan Ringer
2020-03-03python38: 3.8.1 -> 3.8.2Jonathan Ringer
2020-02-29Merge master into staging-nextFrederik Rietdijk
2020-02-28pypy{,3}: use openssl_1_1Emily
"We now support building PyPy with OpenSSL 1.1 in our built-in _ssl module, as well as maintaining support for previous versions." -- https://pypy.readthedocs.io/en/latest/release-pypy2.7-v5.6.0.html
2020-02-19python: execute pythonImportsCheckPhase in subshellJonathan Ringer
Execute in subshell so that the cwd returns back to the original directory. This is important as it enables pythonImportsCheck to work with checkPhase
2020-02-06Merge master into staging-nextFrederik Rietdijk
2020-02-06python39: 3.9.0a2 -> 3.9.0a3Frederik Rietdijk
2020-01-28Merge branch 'staging' into glibc230Maximilian Bosch
Conflicts: pkgs/applications/misc/vit/default.nix
2020-01-28Merge master into staging-nextFrederik Rietdijk
2020-01-23Merge branch 'staging' into glibc230Maximilian Bosch
2020-01-15Merge pull request #77610 from LnL7/darwin-stdenv-python3Frederik Rietdijk
darwin-stdenv: bootstrap with python3
2020-01-14pythonPackages.venvShellHook: initFrederik Rietdijk
This is a hook that loads a virtualenv from the specified `venvDir` location. If the virtualenv does not exist, it is created.
2020-01-14cpython: fetch darwin-libutil.patch to nixpkgsLuka Blaskovic
python3 is now required buildInput for glibc>=2.29. Remove fetchpatch to solve infinite recursion in glibc bootstrap process.
2020-01-13stdenv: bootstrap darwin with python3Daiderd Jordan
- Replaced python override from the final stdenv, instead we propagate our bootstrap python to stage4 and override both CF and xnu to use it. - Removed CF argument from python interpreters, this is redundant since it's not overidden anymore. - Inherit CF from stage4, making it the same as the stdenv.
2020-01-08python: Add support for installing Python eggsadisbladis
2019-12-30python.pkgs.wrapPython: get rid of warningJan Tojnar
When `makeWrapperArgs` variable is not set, `declare -p makeWrapperArgs` will return with 1 and print an error message to stderr. I did not handle the non-existence case in b0633406cb70e0e4ae3470a6b49e32b38d99ac16 because I thought `mk-python-derivation` will always define `makeWrapperArgs` but `wrapProgram` can be called independently. And even with `mk-python-derivation`, `makeWrappers` will not be set unless explicitly declared in the derivation because of https://github.com/NixOS/nix/issues/1461. I was lead to believe that because the builds were succeeding and I confirmed that the mechanism fails when the variable is not defined and `-o nounset` is enabled. It appears that `wrapPython` setup hook is not running under `-o nounset`, though, invaldating the assumption. Now we are checking that the variable exists before checking its type, which will get rid of the warning and also prevent future error when `-o nounset` is enabled in the setup hook. For more information, see the discussion at https://github.com/NixOS/nixpkgs/commit/a6bb2ede232940a96150da7207a3ecd15eb6328
2019-12-28python.pkgs.wrapPython: fix string makeWrapperArgsJan Tojnar
Bash takes an assignment of a string to an array variable: local -a user_args user_args="(foo bar)" to mean appending the string to the array, not parsing the string into an array as is the case when on the same line as the declaration: local -a user_args="(foo bar)" b0633406cb70e0e4ae3470a6b49e32b38d99ac16 extracted the declaration before the newly branched code block, causing string makeWrapperArgs being added to the array verbatim. Since local is function scoped, it does not matter if we move it inside each of the branches so we fix it this way.
2019-12-26Merge pull request #76283 from jtojnar/python-mwaworldofpeace
python.pkgs.wrapPython: fix makeWrapperArgs
2019-12-25Merge branch 'staging-next' into stagingJan Tojnar
2019-12-25Merge branch 'master' into staging-nextJan Tojnar
2019-12-23python.pkgs.wrapPython: fix makeWrapperArgsJan Tojnar
When `makeWrapperArgs` is a Bash array, we only passed the first item to `wrapProgram`. We need to use `"${makeWrapperArgs[@]}"` to extract all the items. But that breaks the common string case so we need to handle that case separately.
2019-12-19python37: 3.7.5 -> 3.7.6Frederik Rietdijk
2019-12-19python39: 3.9.0a1 -> 3.9.0a2Frederik Rietdijk
2019-12-19python38: 3.8.0 -> 3.8.1Frederik Rietdijk
2019-12-19python36: 3.6.9 -> 3.6.10Frederik Rietdijk
2019-12-16python: remove _manylinux.pyAndreas Rammhold
This will turn manylinux support back on by default. PIP will now do runtime checks against the compatible glibc version to determine if the current interpreter is compatible with a given manylinux specification. However it will not check if any of the required libraries are present. The motivation here is that we want to support building python packages with wheels that require manylinux support. There is no real change for users of source builds as they are still buildings packages from source. The real noticeable(?) change is that impure usages (e.g. running `pip install package`) will install manylinux packages that previously refused to install. Previously we did claim that we were not compatible with manylinux and thus they wouldn't be installed at all. Now impure users will have basically the same situation as before: If you require some wheel only package it didn't work before and will not properly work now. Now the program will fail during runtime vs during installation time. I think it is a reasonable trade-off since it allows us to install manylinux packages with nix expressions and enables tools like poetry2nix. This should be a net win for users as it allows wheels, that we previously couldn't really support, to be used.
2019-12-13Fix manylinux packagesTobias Pflug
Make sure lib outputs are used where applicable.
2019-12-05manylinux packages for PythonFrederik Rietdijk
This adds three lists with manylinux dependencies as well as three packages that include all the manylinux dependencies.
2019-12-02pythonInterpreters: remove unnecessary recFrederik Rietdijk
2019-11-24Merge staging-next into stagingFrederik Rietdijk
2019-11-22update-python-libraries: ignore pyprojectFrederik Rietdijk
2019-11-21python3: add pythonForBuild as parameter, fixes python3MinimalFrederik Rietdijk
`pythonForBuild` exists for cross-compilation. When one overrides python, one needs to ensure pythonForBuild matches.
2019-11-21python3Minimal: 3.7.4 -> 3.7.5Frederik Rietdijk
Base it on python37 so we ensure the package remains up to date.
2019-11-20Merge master into staging-nextFrederik Rietdijk
2019-11-20python39: init at 3.9.0a1Frederik Rietdijk
It's a year until the final release but this will give a chance to test out certain features and how it integrates with other packages. https://www.python.org/dev/peps/pep-0596/
2019-11-20pythonPackages.pipBuildHook: fix unbound variableJan Tojnar
for compatibility with set -u
2019-11-05Merge staging-next into stagingFrederik Rietdijk
2019-11-05Merge master into staging-nextFrederik Rietdijk
2019-11-04Merge pull request #72347 from NixOS/bash-no-undef-varsJohn Ericson
treewide: `set -u` everywhere
2019-11-03update-python-libraries: update usage commentsJonathan Ringer
2019-11-03Merge staging-next into stagingFrederik Rietdijk
2019-11-03python35: 3.5.8 -> 3.5.9Frederik Rietdijk
There were no new changes in version 3.5.9; 3.5.9 was released only because of a CDN caching problem, which resulted in some users downloading a prerelease version of the 3.5.8 .xz source tarball. Apart from the version number, 3.5.9 is identical to the proper 3.5.8 release.
2019-11-03pythonPackages.setuptoolsBuildHook: fix debug messageDmitry Kalinkin
2019-11-01treewide: `*Phase(s)?` variables are optionalJohn Ericson
If these aren't defined, the stdenv defaults are used in the `*Phase` case, or no extra phases are done, in the `*Phases` case.
2019-11-01treewide: Make still dont* Variables are optional in most casesJohn Ericson
Go beyond the obvious setup hooks now, with a bit of sed, with a skipped case: - cc-wrapper's `dontlink`, because it already is handled. Also, in nix files escaping was manually added. EMP
2019-10-29python35: 3.5.7 -> 3.5.8Frederik Rietdijk
2019-10-26pypy: fix build on darwinMario Rodas
2019-10-22pythonInterpreters.graalpython37: initFrederik Rietdijk
Add an interpreter with package set for graalpython 3.7.
2019-10-20python2: 2.7.16 -> 2.7.17Frederik Rietdijk
Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>