Dino Viehland wrote:
Michael wrote:
http://ironpython-urls.blogspot.com/2009/10/distributing-ironpython-
packages.html
I hope to get committed to Python 2.6, as a compatibility fix, a
separate PEP 370 site-packages folder for IronPython - both in site.py
and distutils, plus get distutils compatible with IronPython.
Not sure if I can get this done before IronPython 2.6 RTM, but assuming
I succeed the IronPython installer could create this directory if it
doesn't exist.
I'll look at making sure our WiX scripts create the directory during
install.
For the "implementation specific folder to the path" are you thinking
"IronPython\Python26\site-packages" or "Python\IronPython26\site-packages"?
There is a discussion about this on Python-dev at the moment. Christian
Heimes (PEP 370 author) is suggesting
"Python\IronPython26\site-packages" which would have been my suggestion
anyway.
It may require the implementation of sys.vm or similar - although
whether adding a new sys attribute in a minor point release of Python
2.6 I'm not sure. Hopefully we'll get something into Python 2.6 though.
Michael
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
