We did have discussion on this on the alias before that brought the __future__ magic as one option. Jim and I are thinking about the right approach, the __future__ is absolutely a valid candidate we are looking at. We surely want to find the right answer before 1.0
Martin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Jonathan Jacobs > Sent: Monday, August 15, 2005 1:08 PM > To: Discussion of IronPython > Subject: Re: [IronPython] Iron Python Library Usage > > Martin Maly wrote: > > It is not obvious how to approach this, but definitely our > goal is to > > make sure that we stay true to the Python lanugage and its > libraries > > and as I said, it is our focus from now on to make progress on the > > libraries and built-in modules etc. > > What about __future__ magic? > > -- > Jonathan > > When you meet a master swordsman, > show him your sword. > When you meet a man who is not a poet, > do not show him your poem. > -- Rinzai, ninth century Zen master > _______________________________________________ > users-ironpython.com mailing list > users-ironpython.com@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
