[issue4320] optparse: "1 2 3" should be seen as one string

Georg Brandl added the comment: Closing due to vague report description. -- nosy: +georg.brandl resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue4320] optparse: "1 2 3" should be seen as one string

Gregg Lind <[EMAIL PROTECTED]> added the comment: Can you show an example of this not working? Works fine for me in 2.4/2.5/2.6. -- nosy: +gregg.lind ___ Python tracker <[EMAIL PROTECTED]> __

[issue4320] optparse: "1 2 3" should be seen as one string

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: I had the same need in my small command line client (that uses Cmd.Cmd) and I solved it by using shlex.split() instead of regular string split. I haven't looked at optparse code lately and perhaps it can do the same. -- nosy: +d

[issue4320] optparse: "1 2 3" should be seen as one string

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: (copied from the Optik bug tracker -- I haven't tried to replicate this.) -- components: Library (Lib) messages: 75848 nosy: akuchling severity: normal status: open title: optparse: "1 2 3" should be seen as one string versions: Pyth