On Fri, Sep 18, 2009 at 2:18 PM, René Dudfield <[email protected]> wrote:
> hi, > > Added a numpy/compat.py file from pygame. > > This defines these things for compatibility: > __all__ = ['geterror', 'long_', 'xrange_', 'ord_', 'unichr_', > 'unicode_', 'raw_input_'] > > > geterror() is useful for exceptions compatible between py3k and pyv2... > > As in py3k you can't do this: > except ImportError, e: > > So with geterror() it's like this: > except ImportError: > e = compat.geterror() > > > The other ones are just compatibility versions of stuff that's missing. > > > If numpy/compat.py is the wrong place please let me know. > > > cheers, > > > ps. Also... I've asked Lenard, and Marcus from the pygame project if > they mind giving their py3k related code from the LGPL pygame to numpy > and Marcus has said yes. Marcus doesn't have the time for (yet > another) project... but is willing to answer questions if we have any > issues. Haven't heard back from Lenard yet... so better wait off > before importing the pygame code into numpy until he gives the all > clear. > > pps. I was wrong about the -3 flag for python2.6... that only warns > about stuff it knows 2to3 can not handle. 2to3 comes with python2.6 > as well as python3.0/3.1. > Thanks Rene, I'll take a look at this stuff when I get home. Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
