Am 28.07.13 00:36, schrieb Paul Moore:
On 27 July 2013 21:14, Steve Dower steve.do...@microsoft.com
mailto:steve.do...@microsoft.com wrote:
Any chance of this being made optional when installing? It provides
no benefit for people who prefer to associate scripts with an editor
On 30 July 2013 18:24, Martin v. Löwis mar...@v.loewis.de wrote:
Personally, I don't know how to do this so someone else would have to -
It seems that this was settled as fine as-is; if you ever wanted to
allow this to be specifically enabled, you'd have to do three things
Thanks, Martin -
On 28 July 2013 00:30, Steve Dower steve.do...@microsoft.com wrote:
Another issue to consider is that the modification to PATHEXT can't be
undone when Python is uninstalled, unless each installation adds another
.PY and each uninstall removes only one (so my PATHEXT would look like
On 28 July 2013 00:30, Steve Dower steve.do...@microsoft.com wrote:
And if you change the association after the fact, you're presumably just
as capable
of changing PATHEXT.
Not if the association is changed by another installer (presumably with
the user's explicit permission). It would be
On 28 July 2013 08:36, Paul Moore p.f.mo...@gmail.com wrote:
The PEP for pyz and pwz hasn't been accepted yet. If it does, then yes pyz
should be treated the same way (and we can have the same debate about pwz as
we do about pyw :-))
Oops, thanks for the reminder. I'll nudge Daniel about that
: 7/28/2013 1:00
To: Steve Dowermailto:steve.do...@microsoft.com
Cc: Martin v. Löwismailto:mar...@v.loewis.de; Python
Devmailto:python-dev@python.org
Subject: Re: [Python-Dev] Adding Python scripts to PATHEXT on Windows
On 28 July 2013 00:30, Steve Dower
steve.do...@microsoft.commailto:steve.do
On 23 July 2013 17:33, Paul Moore p.f.mo...@gmail.com wrote:
On 23 July 2013 17:11, Martin v. Löwis mar...@v.loewis.de wrote:
Am 15.07.13 10:26, schrieb Paul Moore:
Does anyone have any objections to this? I could try to write a patch,
but I know next to nothing about building MSIs, so if
On 27 July 2013 21:14, Steve Dower steve.do...@microsoft.com wrote:
Any chance of this being made optional when installing? It provides no
benefit for people who prefer to associate scripts with an editor and may
be a source of confusion/complaints.
Personally, I don't know how to do this
From: Paul Moore p.f.mo...@gmail.com
I'm a bit confused by your comment about people who prefer to associate
scripts
with an editor, though. This is only done in precisely those situations when
the installer associates .py scripts with py.exe (the launcher). So if you
switch that off, you
Am 15.07.13 10:26, schrieb Paul Moore:
Does anyone have any objections to this? I could try to write a patch,
but I know next to nothing about building MSIs, so if any of the
installer experts could help that would be fantastic.
It's fine with me. I could write the patch, but will likely
On 23 July 2013 17:11, Martin v. Löwis mar...@v.loewis.de wrote:
Am 15.07.13 10:26, schrieb Paul Moore:
Does anyone have any objections to this? I could try to write a patch,
but I know next to nothing about building MSIs, so if any of the
installer experts could help that would be
With the addition of the Python launcher (PEP 397), Python scripts on
Windows are executable in much the same way as on Unix. However, out of
the box it is still not quite possible to use Python scripts. This is
because the .py extension is not registered with Windows in the PATHEXT
environment
Sounds good to me - in the long run it may allow us to drop the Windows exe
wrappers when installing scripts on Windows.
Cheers,
Nick.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
+1
BTW: I use lots of *.py-executables on Linux and OSX, so different extension
don't bother me.
Gerald
Am 15.07.2013 um 10:26 schrieb Paul Moore p.f.mo...@gmail.com:
With the addition of the Python launcher (PEP 397), Python scripts on
Windows are executable in much the same way as on
On 15 July 2013 09:40, Nick Coghlan ncogh...@gmail.com wrote:
Sounds good to me - in the long run it may allow us to drop the Windows
exe wrappers when installing scripts on Windows.
That's my motivation. In particular removing pip's exe wrappers to ease
some of the issues being flagged on
On 15 July 2013 18:42, Paul Moore p.f.mo...@gmail.com wrote:
On 15 July 2013 09:40, Nick Coghlan ncogh...@gmail.com wrote:
Sounds good to me - in the long run it may allow us to drop the Windows
exe wrappers when installing scripts on Windows.
That's my motivation. In particular removing
16 matches
Mail list logo
