Page MenuHomeFreeBSD

Make USES=python without argument mean 3.6+.
ClosedPublic

Authored by mat on Feb 2 2021, 8:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 26, 8:35 AM
Unknown Object (File)
Tue, Nov 26, 6:49 AM
Unknown Object (File)
Sat, Nov 23, 8:24 AM
Unknown Object (File)
Sun, Nov 10, 2:19 PM
Unknown Object (File)
Oct 26 2024, 8:52 PM
Unknown Object (File)
Oct 23 2024, 5:04 AM
Unknown Object (File)
Oct 18 2024, 12:10 PM
Unknown Object (File)
Oct 4 2024, 12:47 PM
Subscribers

Details

Summary

This is getting us one step further to deorbitting Python 2.7.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 36673
Build 33562: arc lint + arc unit

Event Timeline

mat requested review of this revision.Feb 2 2021, 8:53 AM

The following ports have to be changed to unbreak bulk -a:

converters/py-webencodings
databases/py-sqlite3
devel/py-Jinja2
devel/py-babel
devel/py-future
devel/py-game_sdl2
devel/py-ply
devel/py-pycparser
devel/py-pytz
devel/py-setuptools
devel/py-setuptools_scm
devel/py-six
devel/py-subversion
devel/scons
dns/py-dnspython
lang/cython
misc/py-tqdm
textproc/py-markupsafe
textproc/py-pygments-25
textproc/py-toml
www/py-html5lib
x11-toolkits/py-tkinter

  • Make USES=python without argument mean 3.6+.
  • Those ports are allowed to build a 2.7 flavor.

The following ports have to be changed to unbreak bulk -a:

Done.

rene added inline comments.
Mk/Uses/python.mk
340

It would also be a good idea to explain this change in the introducery comments at the start of this file.

General question: how are we going to avoid people adding 2.7 support to a port because upstream still supports it?

In D28459#636864, @rene wrote:

General question: how are we going to avoid people adding 2.7 support to a port because upstream still supports it?

I was contemplating a commit hook.

Or just saying something like DON'T DO IT, IF YOU DO, THE PORT WILL BE REMOVED. or something similar and kind.

Fixup doc at the start of python.mk.

mat marked an inline comment as done.Feb 2 2021, 4:59 PM
This revision is now accepted and ready to land.Feb 2 2021, 6:38 PM
This revision was automatically updated to reflect the committed changes.