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

Steven Drucker sdrucker at microsoft.com
Wed Jan 4 00:55:16 CET 2006


A number of bugs seem to have been introduced with the new assembly
loading code:

First off, my assemblies will no longer load if they're named x.y (for
instance, I was using an assembly that was named Aforge.Imaging). This
will break since the code does a .split('.') to find all the names to
load.

Second, the first time that I call AddReferenceToFile doesn't effect the
clr.References list at all, but it adds it the second time. See the
following snippet.

---------------
C:\SHO\private\sdrucker\vizdiff>ip
IronPython 1.0.2194 (Beta) on .NET 2.0.50727.40
Copyright (c) Microsoft Corporation. All rights reserved.
>>> import clr
>>> clr.References
(mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Sy
stem, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
>>>
clr.AddReferenceToFile('C:/code/iplab/AForge/Imaging/bin/Debug/AForgeIma
ging
.Dll')
>>> clr.References
(mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Sy
stem, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
>>>
clr.AddReferenceToFile('C:/code/iplab/AForge/Imaging/bin/Debug/AForgeIma
ging
.Dll')
>>> clr.References
(mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Sy
stem, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
AForgeI
maging, Version=2.2.0.27774, Culture=neutral, PublicKeyToken=null)
>>> 
----------------

Third, this breaks when I try to import the file. (No module named
AForgeImaging):

>>> import AForgeImaging
Traceback (most recent call last):
  File , line 0, in input##12
ImportError: No module named AForgeImaging
>>>

Any assistance would be appreciated...
--S





More information about the Ironpython-users mailing list