[IronPython] Ironclad 0.8 released
Hi all I'm delighted to announce the release of Ironclad v0.8 -- the all-singing, all-dancing CPython API compatibility layer for IronPython -- available now from http://code.google.com/p/ironclad/ . Notable improvements over the last release include: * Ironclad is now a neatly self-contained package -- just copy to your site-packages and 'import ironclad'. * No more silly requirement to call ironclad.shutdown() when you're finished. * A few performance improvements. * Over 900 NumPy tests now pass: in fact, almost all the tests from the core, fft, lib, linalg, ma, oldnumeric and random subpackages. * Over half the .pyds distributed with CPython 2.5 now import cleanly; some of them appear to actually work, including _hashlib and _elementtree. Ironclad grows more stable and mature with every release, and I urge IronPython users to try it out and share their impressions: feedback, whether positive or negative, is always welcomed. Cheers William ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Ironclad 0.8 released
Congratulations... Is x64 fully supported? Shechter. On 29/01/2009, at 13:43, William Reade will...@resolversystems.com wrote: Hi all I'm delighted to announce the release of Ironclad v0.8 -- the all- singing, all-dancing CPython API compatibility layer for IronPython -- available now from http://code.google.com/p/ironclad/ . Notable improvements over the last release include: * Ironclad is now a neatly self-contained package -- just copy to your site-packages and 'import ironclad'. * No more silly requirement to call ironclad.shutdown() when you're finished. * A few performance improvements. * Over 900 NumPy tests now pass: in fact, almost all the tests from the core, fft, lib, linalg, ma, oldnumeric and random subpackages. * Over half the .pyds distributed with CPython 2.5 now import cleanly; some of them appear to actually work, including _hashlib and _elementtree. Ironclad grows more stable and mature with every release, and I urge IronPython users to try it out and share their impressions: feedback, whether positive or negative, is always welcomed. Cheers William ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Ironclad 0.8 released
Still no x64, although the necessary supporting changes are gradually creeping in. I can't give you a timescale, I'm afraid, but every person who asks me about it pushes it up my priority list :-). Dan Shechter wrote: Congratulations... Is x64 fully supported? Shechter. On 29/01/2009, at 13:43, William Reade will...@resolversystems.com wrote: Hi all I'm delighted to announce the release of Ironclad v0.8 -- the all-singing, all-dancing CPython API compatibility layer for IronPython -- available now from http://code.google.com/p/ironclad/ . Notable improvements over the last release include: * Ironclad is now a neatly self-contained package -- just copy to your site-packages and 'import ironclad'. * No more silly requirement to call ironclad.shutdown() when you're finished. * A few performance improvements. * Over 900 NumPy tests now pass: in fact, almost all the tests from the core, fft, lib, linalg, ma, oldnumeric and random subpackages. * Over half the .pyds distributed with CPython 2.5 now import cleanly; some of them appear to actually work, including _hashlib and _elementtree. Ironclad grows more stable and mature with every release, and I urge IronPython users to try it out and share their impressions: feedback, whether positive or negative, is always welcomed. Cheers William ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Ironclad 0.8 released
One more encouragement :) x64 support is important now that people are migrating to Windows Server 2008 hypervisor VMs to run the web application. Dody G. On Thu, Jan 29, 2009 at 3:12 PM, William Reade will...@resolversystems.comwrote: Still no x64, although the necessary supporting changes are gradually creeping in. I can't give you a timescale, I'm afraid, but every person who asks me about it pushes it up my priority list :-). Dan Shechter wrote: Congratulations... Is x64 fully supported? Shechter. On 29/01/2009, at 13:43, William Reade will...@resolversystems.com wrote: Hi all I'm delighted to announce the release of Ironclad v0.8 -- the all-singing, all-dancing CPython API compatibility layer for IronPython -- available now from http://code.google.com/p/ironclad/ . Notable improvements over the last release include: * Ironclad is now a neatly self-contained package -- just copy to your site-packages and 'import ironclad'. * No more silly requirement to call ironclad.shutdown() when you're finished. * A few performance improvements. * Over 900 NumPy tests now pass: in fact, almost all the tests from the core, fft, lib, linalg, ma, oldnumeric and random subpackages. * Over half the .pyds distributed with CPython 2.5 now import cleanly; some of them appear to actually work, including _hashlib and _elementtree. Ironclad grows more stable and mature with every release, and I urge IronPython users to try it out and share their impressions: feedback, whether positive or negative, is always welcomed. Cheers William ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Ironclad 0.8 released
Dody Gunawinata wrote: One more encouragement :) x64 support is important now that people are migrating to Windows Server 2008 hypervisor VMs to run the web application. Contributions welcomed. :-) Michael Dody G. On Thu, Jan 29, 2009 at 3:12 PM, William Reade will...@resolversystems.com mailto:will...@resolversystems.com wrote: Still no x64, although the necessary supporting changes are gradually creeping in. I can't give you a timescale, I'm afraid, but every person who asks me about it pushes it up my priority list :-). Dan Shechter wrote: Congratulations... Is x64 fully supported? Shechter. On 29/01/2009, at 13:43, William Reade will...@resolversystems.com mailto:will...@resolversystems.com wrote: Hi all I'm delighted to announce the release of Ironclad v0.8 -- the all-singing, all-dancing CPython API compatibility layer for IronPython -- available now from http://code.google.com/p/ironclad/ . Notable improvements over the last release include: * Ironclad is now a neatly self-contained package -- just copy to your site-packages and 'import ironclad'. * No more silly requirement to call ironclad.shutdown() when you're finished. * A few performance improvements. * Over 900 NumPy tests now pass: in fact, almost all the tests from the core, fft, lib, linalg, ma, oldnumeric and random subpackages. * Over half the .pyds distributed with CPython 2.5 now import cleanly; some of them appear to actually work, including _hashlib and _elementtree. Ironclad grows more stable and mature with every release, and I urge IronPython users to try it out and share their impressions: feedback, whether positive or negative, is always welcomed. Cheers William ___ Users mailing list Users@lists.ironpython.com mailto:Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com mailto:Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com mailto:Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- nomadlife.org http://nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
[IronPython] Handling the import of scripts
If there a way for me to intercept when IronPython wants to import a script, so I can provide the script text through my own ways. I have a situation where my Python files are not files on the disk, but packed into a zip file. When I go to run a script I can get the source to IronPython to run, but, if that script imports another script that is also in the zip file, I would like to go through my methods of resolving the file, loading it, and passing it back to IronPython. -Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Handling the import of scripts
I'm not sure of a way directly from IronPython, but if you're hosting IronPython you can define your own PlatformAdaptationLayer, which is used to re-define platformy things like import. Here's some info on how to do that: http://www.mail-archive.com/users@lists.ironpython.com/msg06079.html. And here's the PlatformAdaptationLayer I use in AgDLR, for looking in a zip file when import is called: http://github.com/jschementi/agdlr/blob/61ee0134167a546a55cf138ef63edc5d7eb4b830/src/Microsoft.Scripting.Silverlight/BrowserPAL.cs ~js -Original Message- From: users-boun...@lists.ironpython.com [mailto:users- boun...@lists.ironpython.com] On Behalf Of Jeff Slutter Sent: Thursday, January 29, 2009 10:24 AM To: Discussion of IronPython Subject: [IronPython] Handling the import of scripts If there a way for me to intercept when IronPython wants to import a script, so I can provide the script text through my own ways. I have a situation where my Python files are not files on the disk, but packed into a zip file. When I go to run a script I can get the source to IronPython to run, but, if that script imports another script that is also in the zip file, I would like to go through my methods of resolving the file, loading it, and passing it back to IronPython. -Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Handling the import of scripts
Look into using sys.path_hooks and sys.meta_path (see http://www.python.org/dev/peps/pep-0302/). Dave -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Slutter Sent: Thursday, January 29, 2009 10:24 AM To: Discussion of IronPython Subject: [IronPython] Handling the import of scripts If there a way for me to intercept when IronPython wants to import a script, so I can provide the script text through my own ways. I have a situation where my Python files are not files on the disk, but packed into a zip file. When I go to run a script I can get the source to IronPython to run, but, if that script imports another script that is also in the zip file, I would like to go through my methods of resolving the file, loading it, and passing it back to IronPython. -Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
