about summary refs log tree commit diff
path: root/pkgs/top-level/python2-packages.nix
AgeCommit message (Collapse)AuthorFilesLines
2023-08-26python2Packages.ninja: alias it to ninja build toolTheodore Ni1-0/+4
2023-08-03python2.pkgs.wcwidth: add missing python2 dependencyTheodore Ni1-0/+4
2023-08-03python2.pkgs.backports-functools-lru-cache: init at 1.6.6Theodore Ni1-0/+2
2023-06-26python3Packages.pysequoia: init at 0.1.14Doron Behar1-2/+0
Also, make `python3Packages.sequoia` throw a message regarding it's replacement of `python3Packages.sequoia`. The main sequoia-pgp/sequoia repository doesn't ship Python code since 0.25.0, just a binary.
2023-02-05python2Packages.wheel: keep 0.37.1 for python2 since 0.38 dropped supportFrederik Rietdijk1-0/+2
2022-12-16Merge branch 'staging-next' into stagingVladimír Čunát1-0/+4
2022-12-15Merge master into staging-nextgithub-actions[bot]1-0/+4
2022-12-15python2Packages.typing: revert removalFabián Heredia Montiel1-0/+2
This reverts commit ff692673773f18ca8940486f3a020212df2b7e76.
2022-12-15python2Packages.scandir: revert removalFabián Heredia Montiel1-0/+2
This reverts commit 7d4a0668d26c39bfcd1b40b21b7d169cedbfe9aa. Closes https://github.com/NixOS/nixpkgs/issues/205742
2022-12-14python310Packages.six: run testsRobert Schütz1-0/+4
2022-12-10Merge branch 'master' into staging-nextVladimír Čunát1-44/+1
2022-12-09python2Packages.pygobject2: move to python2-modulesRobert Schütz1-0/+2
2022-12-09python2Packages.pygobject3: removeRobert Schütz1-4/+0
2022-12-09python2Packages.gtkme: removeRobert Schütz1-2/+0
2022-12-09python2Packages.idna: removeRobert Schütz1-2/+0
2022-12-09python2Packages.scandir: removeRobert Schütz1-2/+0
2022-12-09python2Packages.pysqlite: removeRobert Schütz1-2/+0
2022-12-09python2Packages.certifi: removeRobert Schütz1-2/+0
2022-12-09python2Packages.typing: removeRobert Schütz1-2/+0
2022-12-09python2Packages.google-apputils: removeRobert Schütz1-2/+0
2022-12-09python2Packages.protobuf: removeRobert Schütz1-5/+0
2022-12-09python2Packages.pygments: removeRobert Schütz1-2/+0
2022-12-09python2Packages.botocore: removeRobert Schütz1-2/+0
2022-12-09python2Packages.s3transfer: removeRobert Schütz1-2/+0
2022-12-09python2Packages.boto3: removeRobert Schütz1-2/+0
2022-12-09python2Packages.pyroma: removeRobert Schütz1-2/+0
2022-12-09python2Packages.pytest-runner: removeRobert Schütz1-2/+0
2022-12-09python2Packages.chardet: removeRobert Schütz1-2/+0
2022-12-09python2Packages.sphinxcontrib-websupport: removeRobert Schütz1-2/+0
2022-12-09python2Packages.sphinx: removeRobert Schütz1-2/+0
2022-12-09python2Packages.marisa: removeRobert Schütz1-4/+0
2022-12-09Merge branch 'staging-next' into stagingVladimír Čunát1-25/+0
2022-12-03python2Packages.numpy: removeRobert Schütz1-2/+0
2022-12-03python2Packages.construct: removeRobert Schütz1-2/+0
2022-12-03python2Packages.pillow: removeRobert Schütz1-5/+0
2022-12-03python2Packages.pyyaml: removeRobert Schütz1-2/+0
2022-12-03python2Packages.markdown: removeRobert Schütz1-2/+0
2022-12-03python2Packages.cheetah: removeRobert Schütz1-2/+0
2022-12-03python2Packages.TurboCheetah: removeRobert Schütz1-2/+0
2022-12-03python2Packages.httpretty: removeRobert Schütz1-2/+0
2022-12-03python2Packages.prettytable: removeRobert Schütz1-2/+0
2022-12-03python2Packages.mutagen: removeRobert Schütz1-2/+0
2022-12-03python2Packages.qpid-python: removeRobert Schütz1-2/+0
2022-11-20python310Packages.cffi: patch closures to work on M1 machinesTheodore Ni1-0/+2
Trusts the libffi library inside of nixpkgs on Apple devices. When Apple's fork of libffi is not detected, cffi assumes that libffi uses a strategy for creating closures (i.e. callbacks) that is in certain cases susceptible to a security exploit. Based on some analysis I did: https://groups.google.com/g/python-cffi/c/xU0Usa8dvhk I believe that libffi already contains the code from Apple's fork that is deemed safe to trust in cffi. It uses a more sophisticated strategy for creating trampolines to support closures that works on Apple Silicon, while the simple approach that cffi falls back on does not, so this patch enables code that uses closures on M1 Macs again. Notably, pyOpenSSL is impacted and will be fixed by this, reported in https://github.com/pyca/pyopenssl/issues/873 Note that libffi closures still will not work on signed apps without the com.apple.security.cs.allow-unsigned-executable-memory entitlement while https://github.com/libffi/libffi/pull/621 is still open (which I haven't tested but is my best guess from reading). I am hopeful that all of these changes will be upstreamed back into cffi and libffi, and that this comment provides enough breadcrumbs for future maintainers to track and clean this up.
2022-10-27pythonPackages: ensure all derivations provide python modulesFrederik Rietdijk1-1/+1
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.
2022-08-05python310Packages.attrs: 21.4.0 -> 22.1.0Sandro Jäckel1-0/+1
2022-06-07python2Packages.lpod: removeRobert Schütz1-2/+0
2022-06-07python2Packages.libcloud: removeRobert Schütz1-2/+0
2022-06-07python2Packages.ipaddr: removeRobert Schütz1-2/+0
2022-06-07python2Packages.wsproto: removeRobert Schütz1-2/+0
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-25 02:58:45 +0000