[IronPython] namespaces and modules in IP2

Dino Viehland dinov at microsoft.com
Mon Nov 10 17:49:08 CET 2008

I think it's largely intentional.  In v1 we exposed namespaces as modules and also did ugly things like supported merging of namespaces and modules.  In V2 we did a bunch of cleanup there and moved the former Python code into the outer layer of the DLR.  That involved also making the namespaces read-only just like other .NET objects.  If there was significant interest we could make them mutable again - if you really would like to see it come back I'd suggest opening a feature on CodePlex and encourage people to vote on it.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Glenn Jones
Sent: Monday, November 10, 2008 3:00 AM
To: users at lists.ironpython.com
Subject: [IronPython] namespaces and modules in IP2

Hi all,

We are working on porting our application from IP1 to IP2. We have reached a bit of code where we relied on System.Windows.Forms being a module (we were monkey patching it) and in IP2 it is now a namespace and we cannot set attributes on it.

We can probably work around the change, but we're not sure whether we should if the change is a regression and a fix is forthcoming.

Is this a regression or an intentional change?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20081110/b6728832/attachment.html>

More information about the Ironpython-users mailing list