summaryrefslogtreecommitdiff
path: root/doc/languages-frameworks/python.section.md (follow)
Commit message (Expand)AuthorAgeFilesLines
* treewide: replace `stdenv.is` in non nix files (#344342)Artturin2024-10-091-1/+1
|\
| * doc/python: correct platform conditionalArtturin2024-09-271-1/+1
| * treewide: replace `stdenv.is` in non nix files•••Continuing e0464e47880a69896f0fb1810f00e0de469f770a Artturin2024-09-271-1/+1
* | python3Packages.mkPythonEditablePackage: correct documentationKirill Radzikhovskyy2024-10-071-1/+1
|/
* python3Packages.mkPythonEditablePackage: initadisbladis2024-09-081-0/+44
* doc/languages-frameworks/python: fix typos (#322267)adisbladis2024-09-011-5/+2
|\
| * doc/languages-frameworks/python: fix typosColin2024-09-011-5/+2
* | python3Packages.psycopg2-binary: Fix pname spellingadisbladis2024-08-301-1/+1
* | python3Packages.psycopg2-binary: init at 2.9.9•••Pscycopg2-binary is normally used in Python development to avoid having to build psycopg2 from source. In nixpkgs we always want ot build from source whenever possible, but it can still be useful to provide a psycopg2-binary package. This "fake" package exists to satisfy a dependency on psycopg2-binary, but still use the build from psycopg2. cc @misuzu https://github.com/nix-community/pyproject.nix/issues/143 adisbladis2024-08-301-1/+4
* | python3Packages.mkPythonMetaPackage: init•••This function exists create a meta package containing [metadata files](https://packaging.python.org/en/latest/specifications/recording-installed-packages/) to satisfy a dependency on a package, without it actually having been installed into the environment. adisbladis2024-08-301-0/+13
|/
* Merge remote-tracking branch 'origin/master' into staging-next•••Conflicts: - pkgs/development/python-modules/pycdio/default.nix Martin Weinelt2024-08-111-12/+8
|\
| * doc/python: don't recommend all-packages.nix for Python applicationsDoron Behar2024-08-071-12/+8
* | Merge master into staging-nextgithub-actions[bot]2024-08-071-2/+12
|\|
| * Merge pull request #332784 from pbsds/doc-python-auto-remove-deps-hook-172296...•••docs/language-frameworks/python: pythonRemoveDepsHook is added automaticallyOTABI Tomoya2024-08-071-0/+4
| |\
| | * docs/language-frameworks/python: pythonRemoveDepsHook is added automaticallyPeder Bergebakken Sundt2024-08-061-0/+4
| * | docs/language-frameworks/python: update python{,2,3}Package aliasesPeder Bergebakken Sundt2024-08-061-2/+8
| |/
* / python312Packages.setuptoolsCheckHook: remove•••The hook relied on the `test` command passed to `setup.py`, which has long been deprecated and finally removed in setuptools 72.0. Martin Weinelt2024-08-061-1/+0
|/
* docs: show `pyproject = true;` instead of `format = "pyproject";`•••every other format is deprecated, so to imply that people should be setting it is misleading (`pyproject = true` should also go away eventually, but is the way until then) Arnout Engelen2024-07-261-1/+2
* doc: Remove indefinite article and ending period from example meta.description•••so that meta.description examples shown in the documentation align with recommendations given in the "Meta attributes" section in pkgs/README.md. The changes were made with the following commands: nix run nixpkgs#silver-searcher -- -l0 'description\s*=\s*"([Aa]n?|[Tt]he)\s' doc \ | xargs -0 nix run nixpkgs#gnused -- -i '' -Ee '/description/s/"([Aa]n?|[Tt]he)\s(.)/"\U\2/' nix run nixpkgs#silver-searcher -- -l0 'description\s*=\s*".*\."' doc \ | xargs -0 nix run nixpkgs#gnused -- -i '' -Ee '/description/s/\."/"/' Alexis Hildebrandt2024-07-201-2/+2
* docs/language-frameworks/python: update relaxDepsHook docsMartin Weinelt2024-06-141-6/+5
* doc/languages-frameworks/python: update contributing sectionnatsukium2024-06-041-1/+16
* doc/languages-frameworks/python: adjust expression to explanationnatsukium2024-06-041-3/+2
* doc/languages-frameworks/python: normalize pname and add descriptionnatsukium2024-06-041-2/+3
* doc/languages-frameworks/python: fix typonatsukium2024-06-041-1/+1
* doc/languages-frameworks/python: add extra information for pythonRelaxDepsHooknatsukium2024-06-041-0/+2
* doc/languages-frameworks/python: clean up build-system•••add setuptools explicitly and remove wheel natsukium2024-06-041-12/+3
* doc/languages-frameworks/python: disable check explicitly and add pythonImpor...natsukium2024-06-041-0/+10
* doc/languages-frameworks/python: update the description for testsnatsukium2024-06-041-19/+20
* doc/languages-frameworks/python: update the description for pypa builder/inst...natsukium2024-06-021-11/+5
* doc: autogenerate python interpreter table (#313408)•••* doc: autogenerate python interpreter table This serves as a practical example on generating documentation by inspection of the evaluated Nixpkgs tree. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>Alejandro Sánchez Medina2024-05-231-10/+1
* Removing FRidh as active maintainer of packages•••In the past I was very active with Python packaging. For several years now I was hardly around as maintainer, so it does not make sense I am listed as a maintainer for these makes. Looking back, I should have removed myself as maintainer already much longer ago. Anyway, better late than never. It's been a fun ride, and I do intend to occasionally contribute to Nixpkgs, but not in the same way it once was. Frederik Rietdijk2024-04-281-4/+0
* Merge remote-tracking branch 'upstream/staging-next' into staging••• Conflicts: pkgs/development/python-modules/apsw/default.nix pkgs/development/python-modules/deal/default.nix pkgs/development/python-modules/kubernetes/default.nix annalee2024-03-281-38/+78
|\
| * treewide: Switch markdown placeholder from "..." to <...>•••We use angle brackets since they look a lot like a placeholder while also being valid nix code, as suggested by roberth here: https://github.com/NixOS/nixpkgs/pull/299554#discussion_r1541797970 Janne Heß2024-03-281-1/+1
| * treewide: Fix all Nix ASTs in all markdown files•••This allows for correct highlighting and maybe future automatic formatting. The AST was verified to work with nixfmt only. Janne Heß2024-03-281-25/+65
| * treewide: Mark Nix blocks in markdown as Nix•••This should help us with highlighting and future formatting. Janne Heß2024-03-281-13/+13
* | python3Packages.setuptoolsBuildHook: delete broken setuptoolsShellHook•••Broken since the switch to PyPA's build/installer in 6c85fff302615c62bf4f632bca661bc48298b0a3. The hook was always janky and maintainers appear to not want its current implementation in-tree. No replacement is currently planned. However, this leaves the path open for future replacements as a broken hook will no longer be installed by default. Thomas Watson2024-03-241-75/+1
|/
* Merge pull request #297347 from tzx/docs-right-location-buildPytonPackage•••doc: document name binding for buildPythonPackage Martin Weinelt2024-03-211-2/+3
|\
| * doc: document name binding for buildPythonPackageTimmy Xiao2024-03-211-2/+3
* | doc: Add troubleshooting for Cythonized code and pytest (#293069)•••Cython is a Python compiler that emits native .so modules. By default, python derivations run tests in the wrong directory to see these modules and tests fail. Issue #255262 documents the root cause and solution for this problem. This PR adds a description of the problem and the most common solution to the test troubleshooting list.Sarah Clark2024-03-201-0/+4
|/
* Nix docs: remove `with lib;` from example code•••Following [Best Practices](https://nix.dev/guides/best-practices#with-scopes), `with` is a problematic language construction and should be avoided. Usually it is employed like a "factorization": `[ X.A X.B X.C X.D ]` is written `with X; [ A B C D ]`. However, as shown in the link above, the syntatical rules of `with` are not so intuitive, and this "distributive rule" is very selective, in the sense that `with X; [ A B C D ]` is not equivalent to `[ X.A X.B X.C X.D ]`. However, this factorization is still useful to "squeeze" some code, especially in lists like `meta.maintainers`. On the other hand, it becomes less justifiable in bigger scopes. This is especially true in cases like `with lib;` in the top of expression and in sets like `meta = with lib; { . . . }`. That being said, this patch removes most of example code in the current documentation. The exceptions are, for now - doc/functions/generators.section.md - doc/languages-frameworks/coq.section.md because, well, they are way more complicated, and I couldn't parse them mentally - yet another reason why `with` should be avoided! Anderson Torres2024-03-061-19/+19
* python38: remove•••The end of life for Python 3.8 is scheduled for 2024/10. As such it cannot be a part of NixOS 24.05, because its support cycle goes past that. Martin Weinelt2024-03-051-2/+0
* doc: Fix typo resulting in broken link in manual•••I was looking at https://nixos.org/manual/nixpkgs/stable/#buildpythonpackage-parameters to import a Python package and noticed that the link for the `hooks` in `pyproject` option is broken due to a typo (used <kbd>0</kbd> instead of <kbd>)</kbd>). Signed-off-by: Mihai Maruseac <mihai.maruseac@gmail.com> Mihai Maruseac2024-02-261-1/+1
* Merge master into staging-nextgithub-actions[bot]2024-02-201-37/+45
|\
| * mk-python-derivation: Add build-system argument•••Much like the previous commit that adds dependencies & optional-dependencies this aligns PEP-517 build systems with how they are defined in PEP-518/PEP-621. The naming `build-system` (singular) is aligned with upstream Python standards. adisbladis2024-02-181-16/+17
| * mk-python-derivation: Add dependencies & optional-dependencies arguments•••Since https://github.com/NixOS/nixpkgs/pull/161835 we've had the concept of `passthru.optional-dependencies` for Python optional deps. Having to explicitly put optional-dependencies in the passthru attrset is a bit strange API-wise, even though it semantically makes sense. This change unifies the handling of non-optional & optional Python dependencies using the names established from PEP-621 (standardized pyproject.toml project metadata). adisbladis2024-02-181-26/+33
* | pythonCatchConflictsHook: improve docsDavHau2024-02-131-1/+1
|/
* doc/python: update buildPythonApplication example•••It is fine to use `with` on the inputs, since that increases the overall readability of the package. Removes `wheel` from `nativeBuildInputs`, since it is a result of cargo culting from an earlier setuptools example, that was wrong, and it is not required, since it is provided by setuptools itself. Martin Weinelt2024-01-011-6/+5
* doc: fix python-updates branch name•••The python-updates branch was formerly called python-unstable, but the new branch name was never mentioned in the docs. This commit changes the branch name in the docs to python-updates. netali2023-12-281-1/+1
* Merge pull request #256816 from Artturin/pythondocpython3packagesArtturi2023-11-101-7/+7
|\
| * doc/python: use python3Packages instead of python3.pkgs•••Allows splicing to work correctly from issue 211340 >> 3: Discourage using package sets like python3.pkgs "directly" > I think about 8 years ago I introduced this and it has been a clear mistake. Since then this pattern was copied throughout. We should indeed go to pythonPackages and also move the helpers such as buildEnv and withPackages into the package set, like haskell already had before. - FRidh Artturin2023-09-231-7/+7