I, too, wish that Python had class decorators. However, given that Python 3000 is decidedly and explicitly not backwards-compatible with Python 2.x, it seems clear that there should eventually be two flavors of IronPython -- 2.x-compatible and 3000-compatible. And I'd be concerned about adding Py3-specific features to IP2x unless Py2x does likewise.
On the other hand, what harm can there be in "from future import class_decorators"? On Feb 4, 2008 10:44 AM, Keith J. Farmer <[EMAIL PROTECTED]> wrote: > Can I resurrect this forgotten soul? > http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=13583 > > Having just finished working on LINQ to SQL, I'm convinced that future > LINQ providers will be making heavy use of .NET attributes not just on > properties, but on classes themselves. Being able to express these > attributes in IronPython is a tremendous bonus. That there be one and only > one way to express these is paramount. > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
