osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Python-Dev] Status of PEP 397 - Python launcher for Windows


On 21/02/2012 2:54 AM, Mark Lawrence wrote:
> On 18/02/2012 05:24, Mark Hammond wrote:
...

>> * Write some user-oriented docs.
>
> The section in the docs "Using Python on Windows" would need to be
> updated, but would this have to happen for every current version of Python?

I'm not sure what docs you are referring to here?

> The docs here
> https://bitbucket.org/vinay.sajip/pylauncher/src/tip/Doc/launcher.rst
> are in my view possibly overkill, what do the rest of you think?

Even though I had no input into those docs, I actually think they are 
fairly good and can't see what should be dropped.  It may make sense to 
split the docs so there is a separate "advanced" doc page.  Further, I 
think there is something that could be added to those docs - the use of 
PATHEXT and the fact that once the shebang line is in place, a 
command-prompt could do just "hello.py" rather than needing "py hello.py".

> The ouput from py --help seems fine but nothing happens when pyw --help
> is entered, is this by accident or design?

I guess "accident" - or more accurately, the lack of doing anything 
special.  It could be useful to have that display a message box with the 
usage - while that would break "pyw --help > out.txt", I doubt that 
really is useful for anyone.  Alternatively, instead of trying to 
display all the usage in "pyw --help", it could display a short message 
indicating what the program is for and refer to "py.exe --help" for more 
information.  Possibly a plain "pyw" (with no args) could do the same 
thing - nothing useful happens in that case either.

>> Thoughts or comments?
>>
>> Mark
>
> A cracking bit of kit :)

Thanks!  Vinay's implementation is great, I agree.

Thanks,

Mark