summaryrefslogtreecommitdiff
path: root/pkgs/development/interpreters/python (follow)
Commit message (Expand)AuthorAgeFilesLines
* Merge master into staging-nextnixpkgs-ci[bot]2025-04-132-28/+3
|\
| * python39: drop before the 25.05 branch-off•••End of security support is scheduled for 2025-10-31, which does not cover the complete 25.05 release cycle. Martin Weinelt2025-04-132-28/+3
* | Merge remote-tracking branch 'origin/master' into staging-nextK9002025-04-081-1/+1
|\|
| * Revert "treewide: replace `rev` with `tag`"•••This reverts commit 65a333600d5c88a98d674f637d092807cfc12253. This wasn't tested for correctness with something like fodwatch [0], and should not have been (self-)merged so quickly, especially without further review. It also resulted in the breakage of at least one package [1] (and that's the one we know of and was caught). A few packages that were updated in between this commit and this revert were not reverted back to using `rev`, but other than that, this is a 1:1 revert. [0]: https://codeberg.org/raphaelr/fodwatch [1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e4587d75882aebc21a04bee960418f8ce9 Winter2025-04-081-1/+1
* | Merge remote-tracking branch 'origin/master' into staging-nextK9002025-04-071-1/+1
|\|
| * treewide: replace `rev` with `tag`Pol Dellaiera2025-04-071-1/+1
* | Merge master into staging-nextnixpkgs-ci[bot]2025-04-052-13/+28
|\|
| * python3: Fixing excessive memory usage for overriden python in cross-compile ...Martin Weinelt2025-04-042-13/+28
| |\
| | * python3: Remove unneeded override in `passthruFun`•••`pythonOnBuildForHost` is already overriden when it is passed to `passthruFun` remove redundant override. Performace is slightly better ~200MB less memory. Timothy Gallion2025-04-021-5/+1
| | * python3: Fixing excessive memory usage for overriden python•••An attempt to address #338231. The current release of nixpkgs takes over 20GB of memory to evaluate python when the interpreter is overriden. This adds memoization to the spliced python packages to avoid evaluating all the commbinations of overrides. Timothy Gallion2025-04-021-8/+27
* | | Merge staging-next into stagingnixpkgs-ci[bot]2025-04-031-2/+3
|\| |
| * | pythonInterpreters.pypy39_prebuilt: put deprecation behinde allowAliasesjopejoe12025-04-031-2/+3
* | | Merge staging-next into stagingnixpkgs-ci[bot]2025-04-021-1/+6
|\| |
| * | python3: disable static darwin buildsJörg Thalheim2025-04-021-1/+6
| |/
* | Merge remote-tracking branch 'upstream/staging-next' into stagingSilvan Mosberger2025-04-0218-1406/+1833
|\|
| * treewide: Format all Nix files•••Format all Nix files using the officially approved formatter, making the CI check introduced in the previous commit succeed: nix-build ci -A fmt.check This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153) of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166). This commit will lead to merge conflicts for a number of PRs, up to an estimated ~1100 (~33%) among the PRs with activity in the past 2 months, but that should be lower than what it would be without the previous [partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537). Merge conflicts caused by this commit can now automatically be resolved while rebasing using the [auto-rebase script](https://github.com/NixOS/nixpkgs/tree/8616af08d915377bd930395f3b700a0e93d08728/maintainers/scripts/auto-rebase). If you run into any problems regarding any of this, please reach out to the [formatting team](https://nixos.org/community/teams/formatting/) by pinging @NixOS/nix-formatting. Silvan Mosberger2025-04-0118-1406/+1833
* | pytestCheckHook: support inclusion and exclusion of path globs, test items, k...Yueh-Shun Li2025-03-243-8/+165
|\ \ | |/ |/|
| * python3Packages.pytestCheckHook: support enabledTestMarks and disabledTestMarksYueh-Shun Li2025-03-232-0/+8
| * python3Packages.pytestCheckHook: support enabledTestsYueh-Shun Li2025-03-233-7/+47
| * python3Packages.pytestCheckHook: Make disabledTests support sub-expressions•••Wrap each elements of disabledTests with parenthesis so that when __structuredAttrs = true, people could use sub-expressions an element. E.g. ```nix { disabledTests = [ "ClassFoo and test_foo" "test_bar" ]; } Yueh-Shun Li2025-03-232-1/+10
| * python3Packages.pytestCheckHook: support enabledTestPathsYueh-Shun Li2025-03-233-1/+90
| * python3Packages.pytestCheckHook: support deselecting tests via disabledTestPaths•••Pass disabledTestPaths elements containing double colons (::) to --deselect instead of --ignore-glob. Yueh-Shun Li2025-03-092-3/+13
| * python3Packages.pytestCheckHook: append disableTests flags after disabledTest...Yueh-Shun Li2025-03-091-4/+5
* | Merge master into staging-nextnixpkgs-ci[bot]2025-03-211-0/+3
|\ \
| * | python311: fix _ctypes build on darwin•••In Python 3.12+, the -DUSING_APPLE_OS_LIBFFI=1 macro is always set: https://github.com/python/cpython/commit/25590eb5dee5176f3ac60916b19450f8198e7ffc Fixes #390348 Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com> Ihar Hrachyshka2025-03-161-0/+3
* | | Merge master into staging-nextnixpkgs-ci[bot]2025-03-151-2/+2
|\| | | |/ |/|
| * python314: 3.14.0a5 -> 3.14.0a6•••https://docs.python.org/3.14/whatsnew/changelog.html#python-3-14-0-alpha-6 Martin Weinelt2025-03-151-2/+2
* | buildPythonPackage: simplify check-related attribute inheritanceYueh-Shun Li2025-03-071-20/+11
* | python3Packages.pytestCheckHook: add testsYueh-Shun Li2025-03-071-1/+48
* | python3Packages.pytestCheckHook: fix disabledTestPaths glob matching assertion•••Errors in Bash's process substitution doesn't get propagated outside. Replace the process substitution with Python's `-` as /dev/stdin and Bash's heredoc stdin redirection. Yueh-Shun Li2025-03-071-2/+1
|/
* buildPythonPackage: add and use lib inheritanceYueh-Shun Li2025-03-021-6/+8
* buildPythonPackage: sort lib inheritanceYueh-Shun Li2025-03-021-8/+8
* buildPythonPackage: remove obsolete lib inheritanceYueh-Shun Li2025-03-021-1/+0
* buildPythonPackage: format expressionYueh-Shun Li2025-03-021-2/+2
* python310/python311: fix failing tests with openssl >= 3.4Luka Blašković2025-02-182-0/+37
* Merge master into staging-nextnixpkgs-ci[bot]2025-02-171-0/+5
|\
| * python3{9,10}.doc: fix buildSandro Jäckel2025-02-161-0/+5
* | python314: 3.14.0a4 -> 3.14.0a5•••https://docs.python.org/3.14/whatsnew/changelog.html#python-3-14-0-alpha-5 Martin Weinelt2025-02-133-50/+3
* | treewide: replace substituteAll with replaceVarsWolfgang Walther2025-02-101-5/+3
* | bash: Make interactive by default (#379368)K9002025-02-091-4/+4
|\ \
| * | bash: Make interactive the default•••The status quo of `bash` not being interactive is frustrating for many users, because trying to use it interactively is just messed up, and `bashInteractive` is not intuitive and barely discoverable. This was brought to my (and many others) attention by @stahnma in his [talk at CfgMgmtCamp 2025](https://cfp.cfgmgmtcamp.org/ghent2025/talk/YUVUTN/), where he highlighted this as one of the frustrations he ran into when learning Nix. Why this is fine: - No reason for not making interactive the default was given in the original commit (6c6ff6f36ff26932aa730875bd237c8e37210f0e), but probably it was due to the increase in closure size - The closure size only increases by 6.9MiB (19.5%) today, with the added dependency on the store paths for readline and ncurses, which are needed on systems in almost all cases anyways - If somebody really needs to get a more minimal system, they can use the newly-introduced `bashNonInteractive` instead now - Though to apply it consistently, they'll need to do that in an overlay like ``` final: prev: { bash = self.bashNonInteractive; } ``` Or alternatively using the `system.replaceDependencies.replacements` NixOS option approach. While there's also other such `*Interactive` packages that could use the same treatment, `bash` is a great start. This was already attempted before in https://github.com/NixOS/nixpkgs/pull/151227, but was not continued for unknown reason. To avoid stdenv becoming bigger, all uses of bash in the (working) stdenv's are changed to the explicitly non-interactive version here. This commit will however still cause a mass rebuild for all packages (and reverse deps) making use of the default bash. Silvan Mosberger2025-02-051-4/+4
* | | buildPython*: make name-related attributes overridable via overrideAttrs (#37...Martin Weinelt2025-02-081-4/+2
|\ \ \
| * | | buildPython*: make name-relaed attributes overridable via overrideAttrs•••Make name, pname and version overridable via overrideAttrs for Python packgaes constructed with buildPython*. Yueh-Shun Li2025-02-041-4/+2
| | |/ | |/|
* | | buildPython*: Enable direct attribute overriding via overrideAttrs (the stagi...Martin Weinelt2025-02-081-4/+6
|\ \ \
| * | | buildPython*: always specify attributes catchConflicts and dontWrapPythonProg...•••Always specify catchConflicts and dontWrapPythonPrograms. Make them overrideAttrs-overridable. Yueh-Shun Li2025-02-041-4/+6
| |/ /
* | | cpython: provide libuuid for the _uuid module (#377458)•••* util-linuxMinimal: build without pam and shadow These depend on python via audit preventing the use of libuuid from util-linux in python builds. * cpython: provide libuuid for the _uuid module Relying on libuuid offers synchronization primitives, so that "no two processes can obtain the same UUID"¹. [1] https://docs.python.org/3/library/uuid.html#module-uuidMartin Weinelt2025-02-082-0/+3
|\ \ \
| * | | cpython: provide libuuid for the _uuid module•••Relying on libuuid offers synchronization primitives, so that "no two processes can obtain the same UUID"¹. [1] https://docs.python.org/3/library/uuid.html#module-uuid Martin Weinelt2025-01-292-0/+3
* | | | python312: 3.12.8 -> 3.12.9•••https://docs.python.org/release/3.12.9/whatsnew/changelog.html Martin Weinelt2025-02-042-4/+4
* | | | python313: 3.13.1 -> 3.13.2•••https://docs.python.org/release/3.13.2/whatsnew/changelog.html Martin Weinelt2025-02-042-3/+4
* | | | cpython: add isPy313, isPy314 helpersMartin Weinelt2025-02-042-0/+4