Well the reason not is that this has come up several times where someone forgets a future import or something else.
Alex On Tue, Mar 27, 2012 at 3:55 PM, Maciej Fijalkowski <[email protected]>wrote: > On Tue, Mar 27, 2012 at 9:36 PM, Antonio Cuni <[email protected]> wrote: > > Hi Armin, > > > > On 03/26/2012 01:31 PM, arigo wrote: > >> Author: Armin Rigo <[email protected]> > >> Branch: > >> Changeset: r53982:db33a634cb09 > >> Date: 2012-03-26 13:16 +0200 > >> http://bitbucket.org/pypy/pypy/changeset/db33a634cb09/ > >> > >> Log: Python 2.5 compat > > > > do we really want to keep python 2.5 compat? It's not tested, and "what > is not > > tested is broken"... > > > > ciao, > > Anto > > _______________________________________________ > > pypy-dev mailing list > > [email protected] > > http://mail.python.org/mailman/listinfo/pypy-dev > > There is no reason not to. > _______________________________________________ > pypy-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pypy-dev > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero
_______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
