[IronPython] numpy / IronClad?
jmccampbell at enthought.com
Tue Mar 15 15:34:11 CET 2011
On Tue, Mar 15, 2011 at 3:00 AM, Federico Vaggi <vaggi at cosbi.eu> wrote:
> Hey Jason, thanks for all the work on this. I use the enthought python
> distribution, and it appears that the ironpkg package has some conflict with
> installer present in python - here is what happens if you run ironpkg after
> installing it:
> C:\TEMP>ipy ironpkg-1.0.0.py --install
> 118 KB
> C:\TEMP>ironpkg scipy
> Traceback (most recent call last):
> File "C:\Program Files (x86)\IronPython 2.7\ironpkg-script.py", line 8,
> in <mo
> File "C:\Python27\Lib\site-packages\enstaller\main.py", line 19, in
> File "C:\Python27\Lib\site-packages\enstaller\config.py", line 11, in
> File "C:\Python27\Lib\site-packages\enstaller\utils.py", line 1, in
> ImportError: No module named bz2
> My guess is that since python site-lib and ironpython site-lib are on the
> path, the installer tries to look through the python lib first?
> Either way, should be easy to fix, I'll just grab the version from git and
> play around with it.
Hi Federico, the packager was just something quick we put together since
there wasn't an existing one for IronPython and we needed a way to manage
packages. I haven't seen an install of IronPython that has both the CPython
and IronPython site-packages directories in the same path and I'm not
surprised the packager doesn't handle it.
Does putting both site-packages directories in the same path work in
general? It seems like it would lead to issues with getting the wrong
versions of packages, but perhaps not.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users