On 11/10/2016 09:42 PM, Barry Scott wrote:
In this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1360797
It is implied that rpkg has an unspecified problem with GitPython 2.0.
This is preventing the maintainer from updating to the any GitPython 2
release.
I'd like to know if there is in fact a problem with rpkg with GitPython 2.0.
Import error here.
File "/root/code/rpkg/pyrpkg/__init__.py", line 14, in <module>
import git
File "/root/rpkg-env/lib/python2.6/site-packages/git/__init__.py",
line 38, in <module>
from git.config import GitConfigParser # @NoMove @IgnorePep8
File "/root/rpkg-env/lib/python2.6/site-packages/git/config.py", line
25, in <module>
from git.util import LockFile
File "/root/rpkg-env/lib/python2.6/site-packages/git/util.py", line
18, in <module>
from unittest.case import SkipTest
ImportError: No module named case
GitPython >= 2 cannot work with Python 2.6 at all.
If there is a problem it would be nice if the rpkg people could comment on the
difficult of supporting GitPython 2. The python2.6 support question I suspect
can be handled by version checking in any conflicting code.
It seems wrong that rpkg is blocking updating to the latest GitPython,
preventing user of GitPython getting the bugs fixes and (as far as I am aware)
backwards compatible improvements.
Barry
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
--
Regards,
Chenxiong Qi
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
