Re: /usr/bin/python3 deprecation and enforcing /usr/bin/python

Jeremy Stanley <[email protected]>
Newsgroups gmane.linux.debian.devel.python
Message-ID <[email protected]>
On 2025-11-12 10:49:08 -0500 (-0500), Antoine Beaupré wrote:
[...]
>I've been wondering whether it's time we finally make this 
>change. Concretely, I think it means:
>
> 1. deprecating /usr/bin/python3
> 2. shipping Python 3 as /usr/bin/python directly
>
>I think we should do this for Debian 14 (forky), and stop shipping 
>python3 altogether in Debian 15 (?).
[...]

I can understand the need for #2, but I don't see why you'd ever do 
#1. For that matter, the python3 link is still included by upstream 
Cpython when doing a `make install` or in a stdlib-created venv. 
Lots of user-written scripts use python3 in their shebangs. It's not 
harming anything simply by existing, so why deprecate something that 
can't/shouldn't be removed?
-- 
Jeremy Stanley
signature.asc (application/pgp-signature, 963 B)
-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEEl65Jb8At7J/DU7LnSPmWEUNJWCkFAmkUuDtfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk3
QUU0OTZGQzAyREVDOUZDMzUzQjJFNzQ4Rjk5NjExNDM0OTU4MjkACgkQSPmWEUNJ
WCkXMQ//UtC6gurp4vFvrff+hQQiEoxfHRmWEhKNP++kQuNgS+m3A0gda/lzUm5G
U/AbbjcWToEk80ZUtQnKZlfKbwUKrJ5E+4WvonReF8FtwWEH9x8klLy3hIOwrXs5
oBb6TVDzUDUOSBYsOzx356XAHs38flQT9r0JZrgi6LZiH59rQld0TjNGhEXcgk5b
F9J79594dUozL1dqmxjcKiLYebVwGoXgtt1ISxJswWnuV9VzQdU2N06gSLDD5HBm
8ZTbf+A2dhTNaAnOvCok+VIOW1YsIfivTwSLiZ9Y1IL2zKp+SOfNEQftwjUIFFNU
PpyJsxLKzF8L8WpdtcE/YUPK1JuDs5a5epn+Wk2zDhwKC1s68xuJKvvztlPAaI9W
6TBMCEX/mIkVJr5MTDmYoTKSbuI1/xwpxD2nBrQr0jHfi0AsISIQAEdd6+tLKBFg
9BfJvAmVVMdsC9yZdLbI7LIKeJEvfBHk+3dz9pC5hJKX/a2MK6/tqkRCNlpoiU8u
gvDm9QQ8UlbVrCVfRRSnCMJe8cAdTa9t3K/MXV4hezyuUgUOdVyd5EBrbGEGYAi8
QhIHslfAiTfSVnkwTHnVlGUcJi6u57zIjzEyYdbQZsW+Yv5iI5wCDOiC9aVUmBQy
TzWCRcB7x/SiolKVUG+c3syTBrDalEga4c/M9HJHfgjc501zMaA=
=yKCm
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.