New issue 82 by Arfrever...@gmail.com: argparse 1.2 incompatible with
Python 3.1
http://code.google.com/p/argparse/issues/detail?id=82
argparse 1.1 was compatible with Python 3.1 (all 1485 tests were passing).
argparse 1.2 is incompatible with Python 3.1.
Output of tests of argparse 1.2:
$ PYTHONPATH=. python3.1 test/test_argparse.py
Traceback (most recent call last):
File "test/test_argparse.py", line 13, in <module>
from StringIO import StringIO
ImportError: No module named StringIO
It's not only a bug in test suite. If I copy test_argparse.py from argparse
1.1 and try to run tests against argparse 1.2, then there are 1060 errors.
Comment #1 on issue 82 by steven.b...@gmail.com: argparse 1.2 incompatible
with Python 3.1
http://code.google.com/p/argparse/issues/detail?id=82
Thomas, any chance you could take a look at this? The previous releases of
argparse ran on Python 2.3-3.1.
Comment #2 on issue 82 by ThomasMo...@gmail.com: argparse 1.2 incompatible
with Python 3.1
http://code.google.com/p/argparse/issues/detail?id=82
I'll have a look.
Isn't argparse in stdlib since 2.7 (and also in 3.x)?
If so, why do you use the package?
argparse is in stdlib in 2.7 and >=3.2, not 3.1.
Comment #4 on issue 82 by ThomasMo...@gmail.com: argparse 1.2 incompatible
with Python 3.1
http://code.google.com/p/argparse/issues/detail?id=82
Should be fixed by this changeset, please see the commit comment and do a
test:
http://code.google.com/p/argparse/source/detail?r=c1c83cae40ebebe8aeb89f212484a33296bc83be
Please apply the attached patch.
Attachments:
test_argparse.patch 384 bytes
Thanks for the patch. I applied a very similar change, but also "fixed" the
python 2.3 testing issue the same way. I changed the version comparison for
consistency reasons.
Thanks. Please release a new version (1.2.1 or 1.3).
Yeah, 1.2.1 - soon! :)
Comment #9 on issue 82 by ThomasMo...@gmail.com: argparse 1.2 incompatible
with Python 3.1
http://code.google.com/p/argparse/issues/detail?id=82
1.2.1 released!
Thanks again for doing this!