- Copy devel/py-setuptools to devel/py-setuptools44 (for Python 2.7 support)
- Update devel/py-setuptool to 57.0.0 (adding support for Python 3.10)
- Update Mk/Uses/python.mk to chose between py-setuptools and
py-setuptools44 based on Python version
This allows us to have latest setuptools and working Python 3.10
without breaking packages requiring Python 2 support for remaining
reports that require it.
Exp-run showed 3 ports failing to build with latest setuptools and
they were fixed.
PR: 256173
Exp-run by: antoine
Reviewed by: koobs (python)
Approved by: koobs (python)
Differential_Revision: https://reviews.freebsd.org/D30473
This brings python framework in consistense with handbook recommendations
to prefer DISTVERSION and simplifies adding prerelease versions of
python
PR: 255013
Differential Revision: https://reviews.freebsd.org/D29418
Exp-run by: antoine
Approved by: wen@, no objection from python@ or portmgr@
This is getting us one step further to deorbitting Python 2.7.
Reviewed by: rene, antoine, swills
Differential Revision: https://reviews.freebsd.org/D28459
This shared macro was necessary to use with flavors and not break ports with
USES=python (all versions).
All ports that depends on Sphinx are using the latest version on tree.
Approved by: python (with hat)
The devel/py-futures port was removed in r559976 as it was for
Python 2.7 only and no longer referenced in the default cases.
However it was still defined in Mk/Uses/python.mk in PY_FUTURES,
leaving a dangling reference.
Remove it from Mk/Uses/python.mk and from affected ports, as
it was already an empty definition for Python 3.6+
Bump minimal Python version of security/theonionbox to 3.6+
The graphics/py-pillow6 port was removed in r559976 as it was for
Python 2.7 only and no longer referenced in the default cases.
However it was still defined in Mk/Uses/python.mk in PY_PILLOW,
leaving a dangling reference.
Remove it from Mk/Uses/python.mk, leaving only the Python 3
version of that port, graphics/py-pillow, defined and bump the
minimal verion of Python to 3.6 for affected ports.
Since Python-3.8.7 it uses unified with other platforns shared libs naming scheme:
instead of plain .so suffix now it refers to used cpython: .cpython-${PYTHON_SUFFIX}.so
Future Python releases will use this scheme too, it will be hooked via version check
PR: 252057
Approved by: python (wen)
When python package lists are generated by distutils, any file entry that
includes a space will be surrounded in double quotes. This is unnecessary
and causes problems elsewhere such as when stripping ${PREFIX} for staging
or checking the package list in stage-qa.
PR: 248981
Approved by: kevans, portmgr (mat), python (koobs)
Differential Revision: https://reviews.freebsd.org/D26221
- Repocopy textproc/py-sphinx to textproc/py-sphinx18
Update it to 1.8.5 (latest version from 1.8.X).
This version supports Python 2 and 3.
Add test target.
- textproc/py-sphinx: Update to 3.0.2
Python 3 only (3.5+).
Add test target.
- Mk/Uses/python.mk: Add PY_SPHINX
Shared macro to use with flavors and not break
ports with USES=python (all versions).
Python >=3.5 --> textproc/py-sphinx (v3.0.2)
Python < 3.5 --> textproc/py-sphinx18 (v1.8.5)
All ports that uses sphinx were changed to use the new variable
${PY_SPHINX} in the dependency line, exceptions:
* Ports that fails to build with sphinx 3.0.2 because of code.
They are pointing to textproc/py-sphinx18 directly.
There aren't many ports.
* Ports that doesn't know Python flavors.
- Add several patches to fix Sphinx consumers
The most common issues are related with pkg-plist, the output
files from Sphinx changes between versions, keep this dynamically
is the better approach.
This will save time in future sphinx updates.
PR: 245629
Exp-run by: antoine
Much of the Python version selection code had compat shims around to
accomodate the transition from before to with flavors. These can now be
removed.
PR: 243185
Reviewed by: antoine
Differential Revision: https://reviews.freebsd.org/D23084
This was used before flavors were a thing to make sure if you built port
A with some python version, and it needed port B, port B would also be
built with the same python version.
PR: 243185
Reviewed by: antoine
Differential Revision: https://reviews.freebsd.org/D23084
