e9f522eee1
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. |
||
|---|---|---|
| .. | ||
| 2.5.2-ctypes-util-find_library.patch | ||
| 2.5.2-tkinter-x11.patch | ||
| 2.6.2-ssl-threads.patch | ||
| 2.6.5-export-PySignal_SetWakeupFd.patch | ||
| 2.6.5-FD_SETSIZE.patch | ||
| 2.6.5-ncurses-abi6.patch | ||
| 2.7.3-dbm.patch | ||
| 2.7.3-dylib.patch | ||
| 2.7.3-getpath-exe-extension.patch | ||
| 2.7.3-no-libm.patch | ||
| atomic_pyc.patch | ||
| boot.nix | ||
| cross-compile.patch | ||
| default.nix | ||
| deterministic-build.patch | ||
| nix-store-mtime.patch | ||
| no-ldconfig.patch | ||
| python-2.7-distutils-C++.patch | ||
| search-path.patch | ||
| use-correct-tcl-tk-on-darwin.patch | ||