New submission from Bob Alexander :
This program:
import argparse
ap = argparse.ArgumentParser()
ap.add_argument("arg", nargs="*")
ap.parse_args()
Gives usage message:
usage: help_complexity.py [-h] [arg [arg ...]]
It's correct, but unnecessarily complex and chal
Bob Alexander added the comment:
Oops, clarification...
I just reread my kind of long previous post, and realized it wasn't very
explicit that anything concerning file extensions or prepending the current
directory to the PATH apply to Windows only; not Unix (of course).
The "
Bob Alexander added the comment:
Since there seems to be ongoing work on the "which"
function, here are a few more thoughts on this function's
future:
- The existing version does not prepend the current
directory to the path if it is already in the path.
If the current
Bob Alexander added the comment:
Hi R. David --
My report is just to notify y'all of a bug that I noticed. The bug is
causing me no problem, and it's your option as to whether to fix it or not.
I offered a fix, but I haven't the time to perform diffs, etc. You could
make tha
New submission from Bob Alexander:
Python session with 3.5b2
Showing existing error:
>>> from shutil import which
Works OK
>>> which("python")
'C:\\Python27\\python.EXE'
Also works OK
>>> which('C:\\Python27\\python.EXE')
'C:
Bob Alexander added the comment:
Thanks for the note, Martin. I agree that it's a duplicate. (I had done a
brief search for possible dups, but didn't find that one!)
Bob
On Sun, May 17, 2015 at 8:29 PM, Martin Panter
wrote:
>
> Martin Panter added the comment:
>
&g
New submission from Bob Alexander:
Here is simple example of failure to parse arguments that should parse OK. In
the following little program, the second from last line contains an aargument
sequence that parses OK, but the last line should but doesn't.
import argpar
Bob Alexander added the comment:
Thanks Terry. I agree that it's a bug.
And, in the future I'll be more careful about trimming the "history" from
my messages :-)
Bob
--
___
Python tracker
<http://bug
Bob Alexander added the comment:
Thanks for the prompt reply!
Your suggested change does change the behavior to exactly the way I think
it should work by default. Tried it on both Windows 7 and Vista; no popups
when accessing a "mobile mount" drive with nothing in it, just quietly
rep
New submission from Bob Alexander:
Attempting to use os.path.exists on a Windows drive that is a mobile device
mount point with nothing mounted pops up a dialog asking to insert a device.
This makes it impossible to search a set of drives for a specific file without
the possibility of
10 matches
Mail list logo
