Is there any planned python 3.2 support? The way that exception handling currently occurs is not supported in python 3+. Likewise the newer exception handling via the as
keyword is not backwards compatible with python2.5-. There is however a forward and backward compatible fix assuming this is the only issue: http://stackoverflow.com/a/2513890/176978
Comment #1
Posted on Aug 27, 2013 by Grumpy LionComing back to this project after a long hiatus. Python 2.5 is very old. I currently can't run my test suite w/ 2.5 because of problems with the test tools (tox, etc), so I'm contemplating dropping support for versions < 2.6.
Comment #2
Posted on Aug 27, 2013 by Happy CamelAt this point I don't really care about python < 2.6 myself either. Python 3.2 support, however, would be nice.
Comment #3
Posted on Aug 27, 2013 by Grumpy LionIn what way doesn't it work with 3.2? It passes all my unit tests with Python 2.6, 2.7, 3.2 and 3.3. 3.1 is a dead end I believe, and I'm struggling a bit with 3.4, but I think that's just my test setup rearing its ugly head to bite me in the butt.
Comment #4
Posted on Aug 27, 2013 by Happy CamelThis form of exception handling does not work in python 3:
https://code.google.com/p/pylockfile/source/browse/trunk/lockfile/pidlockfile.py#81 https://code.google.com/p/pylockfile/source/browse/trunk/lockfile/pidlockfile.py#189
Comment #5
Posted on Aug 27, 2013 by Grumpy LionMade the jump to Github awhile ago. I have no idea how to snuff out the Google Code repo. Try this instead:
Status: New
Labels:
Type-Defect
Priority-Medium