Thanks for the great work!

Regarding the new zipimport functionality - is it possible to specify an 
embedded resource name for the path to the zip? For example, if I wanted to 
distribute a library by just packaging it up within an assembly? Or is it 
necessary to write the resource out to a file on disk first?

Example:
Instead of: sys.path.insert(0, '/path/lib.zip')
Something like: sys.path.insert(0, 'resource:path.lib.zip')

The primary reason behind wanting to deliver via embedded resource is to 
prevent tinkering/tampering by end users. But there are additional reasons such 
as simpler deployment under Silverlight and not having to deal with versioning 
of extra "satellite" external resources when using our scripting runtime 
environment in multiple projects. All of those issues go away when we can 
package everything directly within the assembly(s).

I am currently using a custom PlatformAdaptationLayer to supply the file 
contents at runtime and msbuild wildcard inclusion of the libraries and all 
subfolders to embed them as resources (something that msbuild tolerates, but 
Visual Studio does not). It would be much cleaner to just use zipimport, as 
well as much easier to maintain (and the distributed assembly would also be 
much smaller due to zip compression).


Keith Rome
Senior Consultant and Architect
MCPD-EAD, MCSD, MCDBA, MCTS-WPF, MCTS-TFS, MCTS-WSS
Wintellect | 770.617.4016 | kr...@wintellect.com
www.wintellect.com

-----Original Message-----
From: ironpython-users-bounces+rome=wintellect....@python.org 
[mailto:ironpython-users-bounces+rome=wintellect....@python.org] On Behalf Of 
Jeff Hardy
Sent: Monday, March 12, 2012 12:53 AM
To: ironpython-users@python.org
Subject: [Ironpython-users] IronPython 2.7.2 Released

On behalf of the IronPython team, I'm happy to announce the final
release IronPython 2.7.2
(http://ironpython.codeplex.com/releases/view/74478). This release
includes everything from IronPython 2.7 and 2.7.1 as well. Like all
IronPython 2.7-series releases, .NET 4 is required to install it.
Installing this release will replace any existing IronPython
2.7-series installation.

Unlike previous releases, the assemblies for all supported platforms
are included in the installer as well as the zip package, in the
"Platforms" directory. IronPython 2.7.2 includes support for .NET 3.5,
.NET 4, Silverlight 4, and Silverlight 5, and preliminary releases for
Mono for Android 4.0 and Windows Phone 7.5. For 2.7.2, the mobile
platforms are previews; they have known issues, and expect them to
change for 2.7.3.

The biggest improvements in IronPython 2.7.2 are:
support for loading libraries from zip archives (the zipimport module);
the sqlite3 module;
many improvements to the pyc.py compiler, such as the ability generate
standalone executables by embedding the IronPython assemblies;
and numerous other bug fixes.

IronPython 2.7.2 is also available for embedding via NuGet. The main
package is IronPython, and the standard library is in
IronPython.StdLib.

A huge thanks to everyone who helped make this release possible; this
wouldn't have been nearly as big a release without your help!
_______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users

_______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users

Reply via email to