[MacPorts] #31935: py26-mercurial_keyring @0.4.5 not compatible with mercurial @1.9.3
MacPorts
noreply at macports.org
Mon Nov 7 11:22:10 PST 2011
#31935: py26-mercurial_keyring @0.4.5 not compatible with mercurial @1.9.3
------------------------------+---------------------------------------------
Reporter: m@… | Owner: and.damore@…
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port: py26-mercurial_keyring
------------------------------+---------------------------------------------
Comment(by m@…):
As mercurial now defaults to python27, does it make sense to provide a
mercurial_keyring port for python26 ''only''? I mean, currently it is not
possible to use mercurial_keyring out of the box. Would it be possible to
provide a port for python27 (assuming that mercurial_keyring is compatible
with python27)?
Regarding the missing missing extension error, I just found out that I had
set `PYTHONPATH` to
`/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
/site-packages` for some reason I do not remember anymore. Of course, in
that way the extension gets found, even by python27. Thanks for the hint!
--
Ticket URL: <https://trac.macports.org/ticket/31935#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list