From marvin.jones at five.ai Mon Nov 2 11:22:17 2020 From: marvin.jones at five.ai (Marvin Jones) Date: Mon, 2 Nov 2020 16:22:17 +0000 Subject: [Wheel-builders] Why does quay.io/pypa/manylinux2014_x86_64 image not have libpython3.x installed? Message-ID: <74aed15d-80d8-1418-3e65-9909d5900ebf@five.ai> It appears to me that whilst the quay.io/pypa/manylinux2014_x86_64 docker image does have the relevant development headers installed for each of the supported Python3 versions (see /opt/python/cp38-cp38/include/python3.8/Python.h, etc.) the corresponding shared object libraries are not installed (libpython3.8.so, etc.) and are missing from /usr/lib64/, or any of the other places I might expect to find them. Is this the case? And if so, why? I (think) I need to link against them when building a pybind11 extension (built with CMake). Marvin Jones. From rddeblois at gmail.com Mon Nov 2 11:50:06 2020 From: rddeblois at gmail.com (R.D. de Blois) Date: Mon, 2 Nov 2020 17:50:06 +0100 Subject: [Wheel-builders] Why does quay.io/pypa/manylinux2014_x86_64 image not have libpython3.x installed? In-Reply-To: <74aed15d-80d8-1418-3e65-9909d5900ebf@five.ai> References: <74aed15d-80d8-1418-3e65-9909d5900ebf@five.ai> Message-ID: Hi Marvin, You do not need (and should not) link with libpython to build extension modules. The rationale is described here: https://www.python.org/dev/peps/pep-0513/#libpythonx-y-so-1 This also applies to manylinux2014, as PEP 599 contains this: libpythonX.Y remains ineligible for inclusion for the same reasons outlined in PEP 513 . Kind regards, rdb On Mon, Nov 2, 2020 at 5:47 PM Marvin Jones wrote: > It appears to me that whilst the quay.io/pypa/manylinux2014_x86_64 > docker image does have the relevant development headers installed for > each of the supported Python3 versions (see > /opt/python/cp38-cp38/include/python3.8/Python.h, etc.) the > corresponding shared object libraries are not installed > (libpython3.8.so, etc.) and are missing from /usr/lib64/, or any of the > other places I might expect to find them. Is this the case? And if so, > why? I (think) I need to link against them when building a pybind11 > extension (built with CMake). > > Marvin Jones. > > _______________________________________________ > Wheel-builders mailing list > Wheel-builders at python.org > https://mail.python.org/mailman/listinfo/wheel-builders > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin at reportlab.com Wed Nov 25 06:07:18 2020 From: robin at reportlab.com (Robin Becker) Date: Wed, 25 Nov 2020 11:07:18 +0000 Subject: [Wheel-builders] Big Sur builds Message-ID: A user reported a bug when installing reportlab from source on 'Big Sur' (macOS 11). I find I have no way to build manylinux wheels (at least on travis with multibuild) for macOS 11. I certainly don't have the hardware (& don't want it). I don't really understand the OSX software compatibility issues, but travis (https://docs.travis-ci.com/user/reference/osx/) doesn't seem to support macos 11 so I guess I will have to wait until it and multibuild do before surfing on. -- Robin Becker From sh at changeset.nyc Mon Nov 30 08:28:35 2020 From: sh at changeset.nyc (Sumana Harihareswara) Date: Mon, 30 Nov 2020 08:28:35 -0500 Subject: [Wheel-builders] pip 20.3 release (heads-up for potential disruption) Message-ID: <448bf5e3-8215-023a-be4e-85b7049a76f2@changeset.nyc> On behalf of the Python Packaging Authority, I am pleased to announce that we have just released pip 20.3, a new version of pip. You can install it by running `python -m pip install --upgrade pip`. This is an important and disruptive release -- we explained why in a blog post last year https://pyfound.blogspot.com/2019/12/moss-czi-support-pip.html . We even made a video about it: https://www.youtube.com/watch?v=B4GQCBBsuNU . Blog post with details: https://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html Highlights include: * **DISRUPTION**: Switch to the new dependency resolver by default. Watch out for changes in handling editable installs, constraints files, and more: https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020 * **DEPRECATION**: Deprecate support for Python 3.5 (to be removed in pip 21.0) * **DEPRECATION**: pip freeze will stop filtering the pip, setuptools, distribute and wheel packages from pip freeze output in a future version. To keep the previous behavior, users should use the new `--exclude` option. * Support for PEP 600: Future ?manylinux? Platform Tags for Portable Linux Built Distributions. * Add support for MacOS Big Sur compatibility tags. The new resolver is now *on by default*. It is significantly stricter and more consistent when it receives incompatible instructions, and reduces support for certain kinds of constraints files, so some workarounds and workflows may break. Please see our guide on how to test and migrate, and how to report issues: https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020 . You can use the deprecated (old) resolver, using the flag `--use-deprecated=legacy-resolver`, until we remove it in the pip 21.0 release in January 2021. In pip 21.0 we will also remove support for Python 2.7. You can find more details (including deprecations and removals) [in the changelog](https://pip.pypa.io/en/stable/news/), and you can find thank-yous and instructions on reporting issues at https://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html . Thank you, Sumana Harihareswara pip project manager Changeset Consulting https://changeset.nyc