Stuart Prescott writes:
> There's a reasonable number of things in /usr/bin with "#!/usr/bin/env
> python" that would be unhappy with this configuration.
I don't think binaries in /usr/bin should be using "#!/usr/bin/env
python". These will also break with virtualenvs. Packaged programs in
Debia
On 16 July 2018 at 08:44, Bastian Venthur wrote:
> Hi,
>
> sorry if this question has been asked before. What is the currently
> recommended way to make `python` point to `python3`? I'd like to have it set
> on a system default level if possible.
>
To answer your question.
Create a brand new vir
Ben Finney wrote:
> To have a command with custom behaviour, the recommendation is the
> general one: put an executable file at ‘/usr/local/bin/python’ with
> whatever behaviour you want.
eeek, please don't!
If a user created an incompatible /usr/local/bin/rm (didn't delete files,
didn't exit 0
Bastian Venthur writes:
> sorry if this question has been asked before. What is the currently
> recommended way to make `python` point to `python3`? I'd like to have
> it set on a system default level if possible.
At a system default level, in Debian, the command ‘python’ (if it is
installed) in
Hi Matthias,
thanks for the reply and the explanation.
Cheers,
Bastian
On 16.07.2018 09:44, Bastian Venthur wrote:
Hi,
sorry if this question has been asked before. What is the currently recommended
way to make `python` point to `python3`? I'd like to have it set on a system
default level if possible.
There is none. Maybe in the far future when Debian doesn't
On Mon, Jul 16, 2018 at 09:44:00AM +0200, Bastian Venthur wrote:
> sorry if this question has been asked before. What is the currently
> recommended way to make `python` point to `python3`? I'd like to have it set
> on a system default level if possible.
We don't recommend it so there is none AFAIK
7 matches
Mail list logo