Everyone seems to like the first half of this simple PEP adding the
extensions. The 3-letter extension for windowed apps can be "pzw"
while the "pyz" extension for console apps stays the same.
The second half, the tool
https://bitbucket.org/dholth/pyzaa/src/tip/pyzaa.py?at=default is less
mature,
As the PEP author I declare we can have 3-letter extensions. It is not
a big deal.
Daniel Holth
On Mon, May 6, 2013 at 4:30 PM, Richard Oudkerk wrote:
> So the bug would just cause .pyzw files to be opened with py instead of pyw?
> Won't this be harmless?
>
> I think the worst that would happen
So the bug would just cause .pyzw files to be opened with py instead of
pyw? Won't this be harmless?
I think the worst that would happen would be that you get a redundant
console window if you are not already running powershell inside a console.
--
Richard
__
On 6 May 2013 20:46, Steve Dower wrote:
> To summarise the bug, when PowerShell invokes a command based on an
> extension in PATHEXT, only the first three characters of the extension are
> used to determine the associated program. I tested this by creating a file
> "test.txta" and adding ".TXTA"
> From: Nick Coghlan [mailto:ncogh...@gmail.com]
> Sent: Friday, May 3, 2013 2348
>
> We don't need examples of arbitrary data file extentions, we need examples
> of 4 letter extensions that are known to work correctly when placed on
> PATHEXT, including when called from PowerShell. In the absence
On Sat, 04 May 2013 11:41:27 +1000
Steven D'Aprano wrote:
>
> > Rather than risk obscure bugs, I would suggest restricting the extensions
> > to 3 characters. For the “Windowed Python ZIP Applications” case, could we
> > use .pzw as the extension instead of .pyzw?
>
> I've had Linux systems whic
On 4 May 2013 07:48, Nick Coghlan wrote:
> We don't need examples of arbitrary data file extentions, we need
> examples of 4 letter extensions that are known to work correctly when
> placed on PATHEXT, including when called from PowerShell. In the
> absence of confirmation that 4-letter extension
Steven D'Aprano writes:
> > Give us a non-MS example, please.
> I'm afraid I don't understand your question.
There were two problems mentioned. Paul worries about 4-letter
extensions under PowerShell. You mentioned conflicts in Linux file
managers. In both cases, a bug on Windows in detecti
On Sat, May 4, 2013 at 4:15 PM, Steven D'Aprano wrote:
> On 04/05/13 15:13, Stephen J. Turnbull wrote:
>>
>> Steven D'Aprano writes:
>>
>> > > Rather than risk obscure bugs, I would suggest restricting the
>> extensions
>> > > to 3 characters. For the “Windowed Python ZIP Applications” case,
>
On 04/05/13 15:13, Stephen J. Turnbull wrote:
Steven D'Aprano writes:
> > Rather than risk obscure bugs, I would suggest restricting the extensions
> > to 3 characters. For the “Windowed Python ZIP Applications” case, could we
> > use .pzw as the extension instead of .pyzw?
+0
> Many o
Steven D'Aprano writes:
> > Rather than risk obscure bugs, I would suggest restricting the extensions
> > to 3 characters. For the “Windowed Python ZIP Applications” case, could we
> > use .pzw as the extension instead of .pyzw?
+0
> Many official Microsoft file extensions are four or more l
On 5/3/2013 6:41 PM, Steven D'Aprano wrote:
Many official Microsoft file extensions are four or more letters, e.g.
docx. I don't see any value in making long-lasting decisions on file
extensions based on (transient?) bugs that aren't our responsibility.
+1
On 03/05/13 20:37, Paul Moore wrote:
On 2 April 2013 01:47, Daniel Holth wrote:
This PEP proposes to fix these problems by re-publicising the feature,
defining the .pyz and .pyzw extensions as “Python ZIP Applications”
and “Windowed Python ZIP Applications”, and providing some simple
tooling t
On 3 May 2013 20:40, "Paul Moore" wrote:
>
> On 2 April 2013 01:47, Daniel Holth wrote:
>>
>> This PEP proposes to fix these problems by re-publicising the feature,
>> defining the .pyz and .pyzw extensions as “Python ZIP Applications”
>> and “Windowed Python ZIP Applications”, and providing some
On 2 April 2013 01:47, Daniel Holth wrote:
> This PEP proposes to fix these problems by re-publicising the feature,
> defining the .pyz and .pyzw extensions as “Python ZIP Applications”
> and “Windowed Python ZIP Applications”, and providing some simple
> tooling to manage the format.
>
There is
On Wed, Apr 3, 2013 at 1:26 AM, Stefan Behnel wrote:
> Brett Cannon, 02.04.2013 19:28:
>> On Tue, Apr 2, 2013 at 1:20 PM, Steve Dower wrote:
>>
python -m pyzaa pack [-o path/name] [-m module.submodule:callable] [-c]
>>> [-w] [-p interpreter] directory:
ZIP the contents of directo
Brett Cannon, 02.04.2013 19:28:
> On Tue, Apr 2, 2013 at 1:20 PM, Steve Dower wrote:
>
>>> python -m pyzaa pack [-o path/name] [-m module.submodule:callable] [-c]
>> [-w] [-p interpreter] directory:
>>>
>>>ZIP the contents of directory as directory.pyz or [-w]
>> directory.pyzw. Adds the execu
On Tue, Apr 2, 2013 at 1:20 PM, Steve Dower wrote:
> > python -m pyzaa pack [-o path/name] [-m module.submodule:callable] [-c]
> [-w] [-p interpreter] directory:
> >
> >ZIP the contents of directory as directory.pyz or [-w]
> directory.pyzw. Adds the executable flag to the archive.
> >
> > ...
> python -m pyzaa pack [-o path/name] [-m module.submodule:callable] [-c] [-w]
> [-p interpreter] directory:
>
>ZIP the contents of directory as directory.pyz or [-w] directory.pyzw.
> Adds the executable flag to the archive.
>
> ...
>
>-p interpreter include #!interpreter as the first li
On 4/1/2013 5:47 PM, Daniel Holth wrote:
users expect .py to be opened with a text editor.
This user expects .py to be executed as an executable script, and thinks
that is the default after an installation of Python on Windows. Windows
has a separate option, Edit, to use to edit things.
Bu
https://docs.google.com/document/d/1MKXgPzhWD5wIUpoSQX7dxmqgTZVO6l9iZZis8dnri78/edit?usp=sharing
PEP: 4XX
Title: Improving Python ZIP Application Support
Author: Daniel Holth
Status: Draft
Type: Standards Track
Python-Version: 3.4
Created: 30 March 2013
Post-History: 30 March 2013, 1 April
21 matches
Mail list logo
