Evan Driscoll added the comment:
One last comment for the time being.
I actually think *both* changes are valuable. Fixing the bug, well, fixes the
bug if you can set the appropriate flag. The improved error message still helps
for existing code and new code that *doesn't* set the
Evan Driscoll added the comment:
> I also think that nargs=## could maybe be special-cased to just ignore
> the A/O designation completely and only check there are enough, but I
> haven't tried this out. Does this seem like a viable approach? Would a
> patch that does that
Evan Driscoll added the comment:
I ran into this issue today. (Or rather a couple weeks ago, and I just
diagnosed it today.)
Reading through the thread and from the bug's age it looks like a fix is
probably not to promising, but Cherniavsky Beni's 2016-04-11 22:03 comment
> Can
Change by Evan Driscoll :
--
nosy: +evaned
___
Python tracker
<https://bugs.python.org/issue9334>
___
___
Python-bugs-list mailing list
Unsubscribe:
Evan Driscoll added the comment:
Hah, I totally forgot about this thing.
I'd suggest a change to the proposed patch. The patched version says:
"In nearly all cases, ``join(head, tail)`` returns a location
equivalent to *path* (the only exception being when there were
multip
New submission from Evan Driscoll :
The documentation for os.path.split says, in part:
"In nearly all cases, join(head, tail) equals path (the only
exception being when there were multiple slashes separating head
from tail)."
But this is not quite true: that's not the *
