[issue23141] Command line long filename not passed correctly

Eric V. Smith added the comment: I'm glad you found it! -- resolution: fixed -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue23141] Command line long filename not passed correctly

Adam Mead added the comment: Hi, I think I've found the problem. After reading you message and seeing your output I went to my laptop which didn't have python installed (using portable on it) and clean installed. Using a clean install with 3.4.2 on a Win8 machine it worked fine. I suspect the i

[issue23141] Command line long filename not passed correctly

Eric V. Smith added the comment: This works fine for me, too, using the Windows version of 3.4.2 downloaded from python.org. 2 questions: - where did you download Python? - which shell are you using? -- nosy: +eric.smith ___ Python tracker

[issue23141] Command line long filename not passed correctly

R. David Murray added the comment: Oh, I see, you are talking about a filename with a space in it. Sorry, my unix-centric eyes didn't see that at first. But like I said, it works fine for me, using python 3.4.1. -- ___ Python tracker

[issue23141] Command line long filename not passed correctly

R. David Murray added the comment: What do you mean by "does not pass the LFN to the script? Everything works fine for me with python3: C:\>test "test lfn.txt" ['C:\\test.py', 'test lfn.txt'] argparse and getopt both depend on sys.argv, by the way, so it's no surprise they didn't have differe

[issue23141] Command line long filename not passed correctly

New submission from Adam Mead: Under windows the following code does not pass the LFN to the script. Nor does any other method I've tried (getopts & argparse) test.py import sys print ('Number of arguments:', len(sys.argv), 'arguments.') print ('Argument List:', str(sys.argv)) for x in range(0