Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #235955 > unrolled thread
| Started by | Henning Follmann <hfollmann@itcfollmann.com> |
|---|---|
| First post | 2021-06-09 16:40 +0200 |
| Last post | 2021-06-09 17:00 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
Bullseye default python Henning Follmann <hfollmann@itcfollmann.com> - 2021-06-09 16:40 +0200
Re: Bullseye default python Dan Ritter <dsr@randomstring.org> - 2021-06-09 17:00 +0200
Re: Bullseye default python David Wright <deblis@lionunicorn.co.uk> - 2021-06-09 17:00 +0200
| From | Henning Follmann <hfollmann@itcfollmann.com> |
|---|---|
| Date | 2021-06-09 16:40 +0200 |
| Subject | Bullseye default python |
| Message-ID | <Co7x8-7e-3@gated-at.bofh.it> |
Hello, I recently update one computer to bullseye. So I noticed that /usr/bin/python is not created. I probably missed the news how this will be handled. I think python never was managed through update-alternatives, /usr/bin/python was just a link to /usr/bin/python2 which was again just a link to python2.7 would it be possible to point /usr/bin/python to python3? Or is 2.7 still the default? -H -- Henning Follmann | hfollmann@itcfollmann.com
[toc] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2021-06-09 17:00 +0200 |
| Message-ID | <Co7Qt-dT-3@gated-at.bofh.it> |
| In reply to | #235955 |
Henning Follmann wrote: > Hello, > I recently update one computer to bullseye. > So I noticed that /usr/bin/python is not created. > I probably missed the news how this will be handled. > I think python never was managed through update-alternatives, > /usr/bin/python was just a link to /usr/bin/python2 > which was again just a link to python2.7 > > would it be possible to point /usr/bin/python to > python3? > Or is 2.7 still the default? I have two bullseye systems here. On one, /usr/bin/python does not exist, but python2, 3 and so forth exist. On the other, /usr/bin/python is a symlink to /usr/bin/python2 Interesting. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-06-09 17:00 +0200 |
| Message-ID | <Co7Qu-dT-5@gated-at.bofh.it> |
| In reply to | #235955 |
On Wed 09 Jun 2021 at 10:39:32 (-0400), Henning Follmann wrote:
> I recently update one computer to bullseye.
> So I noticed that /usr/bin/python is not created.
> I probably missed the news how this will be handled.
> I think python never was managed through update-alternatives,
> /usr/bin/python was just a link to /usr/bin/python2
> which was again just a link to python2.7
>
> would it be possible to point /usr/bin/python to
> python3?
> Or is 2.7 still the default?
>From the wiki:
NOTE: Debian testing (bullseye) has removed the "python" package
and the '/usr/bin/python' symlink due to the deprecation of Python
2. No packaged scripts should depend on the existence of
'/usr/bin/python': if they do, that is a bug that should be
reported to Debian. You can use the 'python-is-python3' or
'python-is-python2' packages to restore an appropriate
'/usr/bin/python' symlink for third-party or legacy scripts.
https://wiki.debian.org/Python
which seems reasonable to me. That seems to correspond to bullets
3 and 4 in PEP394:
Distributors may choose to set the behavior of the python command
as follows:
● python2,
● python3,
● not provide python command,
● allow python to be configurable by an end user or a system administrator.
https://www.python.org/dev/peps/pep-0394/
Cheers,
David.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web