Python" messages, Python 2 development has finished so this is not a
sensible option to use as default.
(It is still kept in the ports tree for now, as some important software
has not been updated to use Python 3).
ok tracey aja mariani rpointel
From https://www.python.org/doc/sunset-python-2/, "We are volunteers who
make and take care of the Python programming language. We have decided
that January 1, 2020, was the day that we sunset Python 2. That means
that we will not improve it anymore after that day, even if someone
finds a security problem in it. You should upgrade to Python 3 as soon
as you can."
already run into it myself. Add comments to hopefully make it simpler
and more understandable for future changes to the default version.
Zero feedback but tests well here, committing before I forget about
it because people will run into this with 6.7.
python cflags are now being honored which means gcc now pukes on the
bogus -OPT:Olimit=0 present in python2-config --cflags. Force-disable
the bogus use of -OPT:Olimit=0. ok kmos@ sthen@
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
lang/python port module. I've not yet come up with a port that
would not need this and one can always set MODPY_TESTDEP to "no"
to prevent the module from touching TEST_DEPENDS.
Idea from afresh1 who pointed out the cpan module already does this.
aja "I support this move."
OK sthen@
- there was never a lang/python3/3.6 (@pkgpath marker for this is present in
current 3.6 plists), python3/3.x was only used for 3.2, so remove these.
- they should probably have originally used "@pkgpath lang/python/3.5" to
trigger updates from 3.5 when 3.5 was removed, but no point adding those
to 3.6 now that 3.7 is the default version. so add @pkgpath lang/python/3.5
markers in 3.7 PLISTs, fixing the upgrade path if old versions were present
(there was previously nothing to trigger 3.5 being removed/updated so
stray packages would be left around).
problem reported by Laurie Tratt
MODPY_TEST_ARGS was not enough to get the tests to run using
MODPY_PYTEST, geo/py-proj.
This adds MODPY_TEST_DIR, which defaults to WRKSRC as is normal, to
allow overriding the subdirectory that tests run in. This isn't
specific to MODPY_PYTEST, it will work for PY_SETUPTOOLS tests also.
OK landry@ sthen@
- sync WANTLIB
- use do-gen instead of post-patch for the "subst and regen
autoconf files" target
- ALL_TARGET needs setting differently between 2.7 and 3.x;
rather than checking against 3.6 for "all", check against 2.7
for "all ./Lib/plat-openbsd6". needed for newer 3.x.
With this all the python ports using pytest do not need to setup their
own do-test taret. Instead "MODPY_PYTEST = Yes" does the job.
from Kurt Mosiejczuk
ok kn@
If needed this allows to overwrite it.
I looks like python preferes C.UTF-8. But Ingo pointed out that on
OpenBSD en_US.UTF-8 is prefered and the former is just a link to the later.
from Kurt Mosiejczuk
ok sthen@
