On 10/21/20 10:06 PM, DJ Lucas via blfs-dev wrote:
On 10/21/2020 7:12 PM, Kevin Buckley via blfs-dev wrote:
On Thu, 22 Oct 2020 at 00:26, Bruce Dubbs via blfs-dev
<blfs-dev@lists.linuxfromscratch.org> wrote:
Currently we have /usr/bin/python -> python2. Is it time to change that
to python3?
Probably a bit too drastic a view, but should we even be propagating
the need to have a bare python?
Interesting point.
I appreciate it can be a convenience when 2 and 3 co-exist but the
price for that convenience across the version change has been high.
My preference would be to not use the bare "python" anywhere, so
that scripts have to be explicit about which major version they want.
It will make things a lot easy when python4 comes along!
As to the convenience link in /usr/bin, I'd look to remove it and tell
people that they can alias the bare "python" if they really, really need
to, but that they have to make the choice to do so: the system won't
be doing it for them.
I've effectively already done this being that I'm deliberately avoiding
Python2, but IIRC, that means removing the symlink after it's installed
(the Python-2.x installation does it automatically) - or a sed to keep
it from being created I guess. I'm going to proceed with this approach.
In LFS, we can make the symlink to p3. For p2 in BLFS, we will use
'make altinstall'. Everything else would be for non-python packages
that either use p2 or create a p2 module.
As to gimp (mentioned earlier in this thread), is excising python2 a
goal of the 3.0 release? It is about the only *major* consumer left.
There are only 22 bugs remaining that are not labeled "feature"
currently targeted for the 3.0 milestone. Many of those are old as well.
https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all&utf8=%E2%9C%93&state=opened&milestone_title=3.0¬[label_name][]=1.%20Feature
I did a git clone (very slow) and looked.
configure.ac:m4_define([python3_required_version], [3.6.0])
meson.build:is_git_repository = run_command('python3', '-c',
Also in NEWS:
The API is GObject Introspected into 2 modules: Gimp and GimpUi.
This means plug-ins can be written in various non-C languages. So
far the following languages have been tested and work well: Python
3, Lua, Javascript and Vala.
(Note: Python 2 is also still working, but considering that this
language is end-of-life since 2020, we don't really care).
So it does look like it will be p3.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
