| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | 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 Mosberger | 2025-04-01 | 1 | -38/+53 |
| * | treewide: change pythonForBuild to pythonOnBuildForHost | Adam Joseph | 2023-11-05 | 1 | -1/+1 |
| * | treewide: makeSetupHook deps -> propagatedBuildInputs | Artturin | 2023-02-07 | 1 | -1/+1 |
| * | makeSetupHook: support depsTargetTargetPropagated | Artturin | 2023-02-07 | 1 | -1/+1 |
| * | Merge branch 'master' into staging-next | Vladimír Čunát | 2023-01-27 | 1 | -5/+3 |
| |\ |
|
| | * | treewide: remove global with lib; statements in pkgs/development | Shawn8901 | 2023-01-26 | 1 | -5/+3 |
| * | | treewide: add names to all setup hooks | Alyssa Ross | 2023-01-19 | 1 | -0/+1 |
| |/ |
|
| * | pythonPackages: ensure all derivations provide python modules•••This adds a test to ensure no new uses of `buildPythonApplication` can
be added to `python-packages.nix`.
Python packages can be grouped into two groups: 1) applications and 2)
packages providing importable modules. In `python-packages.nix` we only
want to have 2). 1) should be in the top-level package set.
To achieve this, all setup hooks need to be marked as being a setup hook.
For the setup hooks in the Python packages set this is done by creating
a new builder, `makePythonHook`.
Because there were issues with splicing, the file importing all the hooks
is converted to an extension. All non-packages were moved out of `python-packages.nix`
into `python-packages-base.nix`. The `keep` argument to `makeScopeWithSplicing
was cleaned up as well; there is no need to keep this one manually in sync
reducing the risk of breaking cross-compilation.
| Frederik Rietdijk | 2022-10-27 | 1 | -2/+2 |
| * | Python: improve cross-compilation•••This changeset allows for cross-compilation of Python packages. Packages
built with buildPythonPackage are not allowed to refer to the build
machine. Executables that have shebangs will refer to the host.
| Frederik Rietdijk | 2019-01-04 | 1 | -1/+2 |
| * | wrap-python: fix pypy site-packages path | Jörg Thalheim | 2018-12-20 | 1 | -1/+1 |
| * | Python: script names now include full path•••Certain programs, like zim, calibre and now also apparently mercurial,
rely on sys.argv[0] providing not just the script name but the full
path.
The Python docs [1] state the following on the matter:
> argv[0] is the script name (it is operating system dependent whether
this is a full pathname or not).
Therefore, scripts should not expect to receive a full path.
Unfortunately some do. While this can be considered a bug, there doesn't
seem any reason not to provide the full path. Therefore we now provide
the full path.
[1]
https://docs.python.org/3.5/library/sys.html?highlight=sys.argv#sys.argv
| Frederik Rietdijk | 2017-01-02 | 1 | -1/+1 |
| * | Python: move wrapPython into own file | Frederik Rietdijk | 2016-09-01 | 1 | -0/+51 |
