Updating module-level globals() raises AttributeError.
vars = {'a': 1, 'b': 2}
globals().update(vars)
print a, b
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
2006/3/27, Rene Olsthoorn [EMAIL PROTECTED]:
On Windows XP, it runs without a problem.
Strange, I can reproduce this on Windows XP too.
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
Hi,
When there will be support for .NET Attributes in IronPython?
Is there any way currently to mark my class as Serializable?
--
Andrzej
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Thanks for the bug report Seo. I can repro this on our current builds and have
filed the bug. I think we'll be able to get this one fixed for beta 5.
Do you want to help develop Dynamic languages on CLR?
Did you run it at the console or from a file you imported?
IronPython will actually use different underlying CLR dictionary objects
depending on how the code gets compiled (which is the reason why this compiles
in one spot but not another).
Do you want to help develop Dynamic languages on CLR?
This is a tough problem... There are two issues here. But the executive
summary here is I'd say the earliest you should *expect* to see this is 1.1,
but if (somehow) we end up with some extra time we might have something in the
1.0 timeframe (but don't hold your breath!).
The first issue
On the topic of decorators and integrating with .NET, it seems that in order to keep IronPython as close to CPython, it would be a good idea to consider adding .NET specific pieces as a library instead of an addition to the language. That way people could write python code that works in IronPython
This is great feedback. And yet another
way we could consider doing this would be something whacky with metaclasses
where we had an attribute-aware metaclass or something like that
But it demonstrates the difficulty in adding support for features like this and
the reason we need to tread
For the purposes of consistency, the attribute decorators would need to apply
everywhere an attribute is able to exist in .NET: types, members, etc.
In the case of Serializable, merely subclassing ISerializable isn't necessarily
the best way, since a class can be decorated with
Hi
I'm using mono 1.1.13.4 and calls to IronPython 1.0 Beta 4 cause a segv.
What version of IronPython works??
Mathew
** (/home/myeates/mono-1.1.13.4/lib/xsp/1.0/xsp.exe:20873): WARNING **:
The class System.Collections.Generic.IDictionary`2 could not be loaded,
used in mscorlib,
1.1.13.4 should work with IronPython, but you seem to be running it inside xsp,
which is a net 1.1 app. Try using 'xsp2'.
Zoltan
On 3/27/06, Mathew Yeates [EMAIL PROTECTED] wrote:
Hi
I'm using mono 1.1.13.4 and calls to IronPython 1.0 Beta 4 cause a segv.
What version
11 matches
Mail list logo