Re: Changing 'Scripts/*.exe'

2022-10-03 Thread dn
On 04/10/2022 14.10, Meredith Montgomery wrote: > r...@zedat.fu-berlin.de (Stefan Ram) writes: > >> Meredith Montgomery writes: >>> Wouldn't it be great if it were portable by default? >> >> I think under Windows there is a division of software >> suggested by Microsoft, a division of

Re: Changing 'Scripts/*.exe'

2022-10-03 Thread Meredith Montgomery
r...@zedat.fu-berlin.de (Stefan Ram) writes: > Meredith Montgomery writes: >>Wouldn't it be great if it were portable by default? > > I think under Windows there is a division of software > suggested by Microsoft, a division of software into > executable code and data (data may change in

[Python-announce] Walk-0 - "Walk, don't run."

2022-10-03 Thread jules
This might be a bit niche, but after using it privately for a couple of years, i've made a first release of Walk, a Python module that provides a mechanism for running commands, where commands are not run if Walk can infer that they would not change any generated files. * An LD_PRELOAD library or

Re: Changing 'Scripts/*.exe'

2022-10-03 Thread Barry Scott
> On 1 Oct 2022, at 16:50, Gisle Vanem via Python-list > wrote: > > Hello list. > > I'm moved my old Python27 installation from > f:\ProgramFiler\Python27 ( == 'ProgramFiles') > to > f:\gv\Python27 The design of Windows installed software makes this hard to do without a lot of

Re: python developer

2022-10-03 Thread Jan van den Broek
2022-10-01, orzodk schrieb: > Jan van den Broek writes: > >> 2022-10-01, Mike Dewhirst schrieb: >> >>>So the answer to your question is signed email is easy and if it becomes >>>popular it has potential to defeat hackers. >> >> Yes, but I'm reading this as a usenet-message (comp.lang.python),

Re: on GNU EMACS's python-mode, loading entire buffer

2022-10-03 Thread Meredith Montgomery
Stephen Berman writes: > On Sun, 04 Sep 2022 16:47:07 -0300 Meredith Montgomery > wrote: > >> Meredith Montgomery writes: >> >>> Meredith Montgomery writes: >>> >>> [...] >>> I would also be interested in a command that restarts the REPL afresh and reloads my buffer --- sort of like

Re: Changing 'Scripts/*.exe'

2022-10-03 Thread Meredith Montgomery
Gisle Vanem writes: > Hello list. > > I'm moved my old Python27 installation from > f:\ProgramFiler\Python27 ( == 'ProgramFiles') > to > f:\gv\Python27 > > and now many 'scripts/*.exe' program fails > to start since the old path to 'Python.exe' > is wrong. > > E.g. 'Scripts/pip2.exe' has

Re: python developer

2022-10-03 Thread orzodk
Jan van den Broek writes: > 2022-10-01, Mike Dewhirst schrieb: > >>So the answer to your question is signed email is easy and if it becomes >>popular it has potential to defeat hackers. > > Yes, but I'm reading this as a usenet-message (comp.lang.python), not as > a mail. You are reading a

Re: Changing 'Scripts/*.exe'

2022-10-03 Thread dn
On 03/10/2022 20.48, Gisle Vanem via Python-list wrote: > dn wrote: > >>> E.g. 'Scripts/pip2.exe' has the path >>> "f:\programfiler\python27\python.exe" hard-coded >>> inside it. >>> >>> Is there a easy way to fix this w/o re-installing this >>> old Python? >> >> Yes, by putting a symbolic-link

Re: Changing 'Scripts/*.exe'

2022-10-03 Thread Gisle Vanem via Python-list
dn wrote: E.g. 'Scripts/pip2.exe' has the path "f:\programfiler\python27\python.exe" hard-coded inside it. Is there a easy way to fix this w/o re-installing this old Python? Yes, by putting a symbolic-link at the old 'programfiler' location which points to the new 'gv' installation. I'm