fails to parse python's version number from "2.7.0+"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
New
|
Undecided
|
Unassigned |
Bug Description
The python2.7 package currently available in Debian experimental patches PY_VERSION to say "2.7.0+". This makes 'python2.7 -V' print "Python 2.7.0+", and that makes zc.buildout crash:
mg@
Develop: '/home/
warning: no files found matching '*.test' under directory 'src'
warning: no files found matching 'sampletests' under directory 'src'
Installing test24.
Generated script '/home/
Installing test25.
Generated script '/home/
Installing test26.
Generated script '/home/
Installing test27.
While:
Installing test27.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File "/home/
File "/home/
File "/home/
return f()
File "/home/
eggs, ws = self._delegated
File "/home/
**kw)
File "/home/
File "/home/
File "/home/
version = re.match(
AttributeError: 'NoneType' object has no attribute 'group'
Ubuntu is also affected: both the python2.7 package in Maverick, and the backports for older releases that are available in the popular ~fkrull/deadsnakes PPA, have the same weird version string.
The following workaround fixes the issue for me:
Index: src/zc/
===
--- src/zc/
+++ src/zc/
@@ -188,7 +188,7 @@ def _get_version(
assert pystring == 'Python'
- version = re.match(
+ version = re.match(
return version
Ubuntu Natty Python version is 2.7.1+
which cause the same issue.
IMHO, there should not be a '+' char in python version string...