My only point is that new decorators shouldn't be included unless they are available in the language. I know Guido said something about them at PyCon but I can't remember what :)<br><br>I have no problems with decorators by the way. Cherrypy (a web framework/library) uses a decorator-ish syntax, so if implementing a library for working around .NET details and IronPython is needed, it would not be out of line to use a decorator. I just think the close CPython and IronPython can be, the better it is for everyone.
<br><br>Eric<br><br><div><span class="gmail_quote">On 3/27/06, <b class="gmail_sendername">Keith J. Farmer</b> <<a href="mailto:kfarmer@thuban.org">kfarmer@thuban.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For the purposes of consistency, the attribute decorators would need to apply everywhere an attribute is able to exist in .NET: types, members, etc.<br><br>In the case of Serializable, merely subclassing ISerializable isn't necessarily the best way, since a class can be decorated with SerializableAttribute instead.
<br><br>Would magic comments be sufficient? eg<br><br>// ATTRIBUTE: Serializeable<br>class MyClass(FooBase):<br> // ATTRIBUTE: MyMemberAttribute<br> def Foo():<br> ....<br><br>(Forgive my Python -- it's a little rusty...)
<br><br>Actually, wasn't there a PEP regarding decorators?<br><br><br><br>_______________________________________________<br>users mailing list<br><a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a>
<br><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br><br><br></blockquote></div><br>