On Tue, Mar 2, 2021 at 4:30 AM Matthias Klose wrote:
> On 2/16/21 5:34 PM, Zack Weinberg wrote:
> > Unpackaged Python-2-only software
> > will continue to exist indefinitely—I am *certain* that I will still
> > need a Python 2 interpreter ten years from now, and I fully expect my
> >
On 2/16/21 5:34 PM, Zack Weinberg wrote:
> Unpackaged Python-2-only software
> will continue to exist indefinitely—I am *certain* that I will still
> need a Python 2 interpreter ten years from now, and I fully expect my
> grandchildren will occasionally trip over Python-2-only software even
> a
On Wed, Feb 17, 2021 at 3:17 PM Dimitri John Ledkov
wrote:
> In Bullseye release file:/usr/bin/python is not reserved, but
> intentionally unused.
That is not good enough. It needs to be reserved.
> In Bullseye release neither deb:python2 nor deb:python3 packages own
> /usr/bin/python.
Yes, I
In Bullseye release file:/usr/bin/python is not reserved, but
intentionally unused.
In Bullseye release neither deb:python2 nor deb:python3 packages own
/usr/bin/python.
This is a Bullseye Release Goal with consensus from all
cpythons/pypys/etc interpreter maintainers, modules maintainers, and
app
Source: what-is-python
Version: 3.8.6-3
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: za...@panix.com
Any system where the unqualified command names ‘python’ and/or
‘python-config’, or the well-known pathname /usr/bin/python, refer to
Python 3, is misconfigured. These
5 matches
Mail list logo