Closed GoogleCodeExporter closed 8 years ago
This bug is supposed to be fixed. Are you running the binaries or from source?
If the latter, try updaring pyzolib.
Original comment by almar.klein@gmail.com
on 15 Apr 2013 at 8:38
I use binary version (one found here
http://code.google.com/p/iep/downloads/detail?name=iep-3.2.linux64.tar.gz&can=2&
q=).
If it is fixed in the VCS I may try to check it out.
Original comment by jbz...@gmail.com
on 15 Apr 2013 at 8:48
Mmm, it seems the bug was not entirely fixed. But now it should be.
The bug was in pyzolib, a dependency of IEP. The easiest way to fix it, I
think, is to take this file:
https://pyzolib.googlecode.com/hg/interpreters/pythoninterpreter.py
... and put it in the library.zip next to the corresponding .pyc file.
Please let me know if this works.
Original comment by almar.klein@gmail.com
on 16 Apr 2013 at 7:40
Still no luck, i put it inside library.zip/pyzolib/interpreters.
jb:)
Original comment by jbz...@gmail.com
on 23 Apr 2013 at 9:44
mmm, perhaps its taking the .pyc instead. You could try removing the .pyc from
the archive. But beware: some archive manager break the zipfile if you try such
a thing...
Original comment by almar.klein@gmail.com
on 30 Apr 2013 at 7:07
As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at
https://bitbucket.org/iep-project/iep/issues
To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X
Issues on Bitbucket can be created by anyone. Commenting on issues requires
login via Bitbucket, Google, Twitter or Github.
Original comment by almar.klein@gmail.com
on 11 Jun 2013 at 2:40
Original issue reported on code.google.com by
jbz...@gmail.com
on 14 Apr 2013 at 6:34