[IronPython] Some new bugs with asssembly loading...

Keith J. Farmer kfarmer at thuban.org
Thu Jan 5 03:23:41 CET 2006


Actually, I'm wondering about the usefulness of an assembly delimiter for the import statement.
 
IE, instead of clr.Add*, you have something more like:
 
from (FooAssembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) import *
 
This maintains the from/import structure in current use -- it just expands the type that the first argument can handle to include, instead of a python library identifier, an assembly reference.  It'd be easier to parse, I think, when dealing with the whole IronPython->Assembly path, rather than hunting for scattered clr.Add* references.

________________________________

From: users-bounces at lists.ironpython.com on behalf of Martin Maly
Sent: Wed 1/4/2006 9:41 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Some new bugs with asssembly loading...



The reason is that clr.References is a tuple without improved formatting. Using tuple was a way to get the idea out there and gather feedback and experiences. Ultimately we may use some custom written tuple-like structure.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4365 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20060104/a677ed69/attachment.bin>


More information about the Ironpython-users mailing list