You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more or less owed to the circumstance that the python default at time of package creation was python2.
From python-3.8.6-0 on the package-bin contains a python link:
#> prun python-3.8.6-0 which python
/pkg/python-3.8.6-0/bin/python
So, to be safe with packages, best stick with python2, python3, 4 ...
This might be a bit surprising, but I think we can live with the fact, that different packages (and package versions) provide different set of commands and thereby mask different sets of commands from outside the package. You are right, the older packages, of course, reflect history. We could add a "python" to elder python3 packages to get "less surprise", but OTOH can we be sure we don't break anything by making changes to existing packages? I'm not sure, a change would be justified.
Example:
The text was updated successfully, but these errors were encountered: