Date: Tue, 16 Nov 2021 23:58:07 -0800 From: Maxim Sobolev <sobomax@freebsd.org> To: ports@freebsd.org, Rene Ladan <rene@freebsd.org> Cc: portmgr@freebsd.org, python@freebsd.org Subject: Bringing back lang/python27 with few modules? Message-ID: <CAH7qZfvBQ0gKEdOn7nTuzAbMOG9LM2DVGyUs9b9PGwNgJTDCAw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--000000000000be8cad05d0f76765
Content-Type: text/plain; charset="UTF-8"
Hi,
I am still a bit concerned with the total removal of python 2.7 year ago
and its support, I think this was a somewhat swift decision that may need
to be re-considered. I understand the urge for portmgr to move base over to
a supported version, but also that caused few important packages to be
dropped out of the FreeBSD without any fix in sight. I am specifically
talking about the PyPy package, which needs 2.7 to bootstrap itself even
when compiled as a "Python3" version.
At the same time we still have a port of for example GCC 4.6, which is like
what, 15 years old? Also things in the tree like jython or micropython are
effectively python 2 implementations, so why are they allowed to be present
while not rock solid and field tried 2.7? In fact jython specifically
recommends using CPython2.7 to byte-compile some of the code that it cannot
chew by itself, so it's somewhat broken as well*.
Is there any chance to bring CPython2.7 at the very least as a NO_PACKAGE
build tool that could be used for such cases now that we have moved most of
the supported packages to 3.x land?
I had always considered FreeBSD to be about "tools not policy", but in this
particular case the policy seemingly took priority over tools and common
sense.
Sorry if I am beating a dead horse here, just wanted to gauge the position
of the project before I go and open yet another bug report.
Thanks!
-Max
*) Like the following:
java.lang.RuntimeException: java.lang.RuntimeException:
Encountered too large method code in
/usr/ports/lang/pypy/work/pypy3.8-v7.3.7-src/rpython/rlib/unicodedata/unicodedb_6_0_0.py
Please provide a CPython 2.7 bytecode file (.pyc) to proceed, e.g. run
python -m py_compile
/usr/ports/lang/pypy/work/pypy3.8-v7.3.7-src/rpython/rlib/unicodedata/unicodedb_6_0_0.py
and try again.
Alternatively provide proper CPython 2.7 execute command via
cpython_cmd property, e.g. call
jython -J-Dcpython_cmd=python
or if running pip on Jython:
pip install --global-option="-J-Dcpython_cmd=python" <package>
*** Error code 255
--000000000000be8cad05d0f76765--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZfvBQ0gKEdOn7nTuzAbMOG9LM2DVGyUs9b9PGwNgJTDCAw>