Actually, it might be easier to assign separate bugs. A number of the old bugs appear to have been fixed. It's hard to track individual items within a bug report.
Jeremy On 2/17/06, Jeremy Hylton <[EMAIL PROTECTED]> wrote: > It is critical, but I hadn't seen the bug report. Feel free to assign > AST bugs to me and assign them a > 5 priority. > > Jeremy > > On 2/17/06, Armin Rigo <[EMAIL PROTECTED]> wrote: > > Hi, > > > > On Tue, Feb 14, 2006 at 09:24:57PM -0800, Neal Norwitz wrote: > > > http://www.python.org/peps/pep-0356.html > > > > There is at least one SF bug, namely "#1333982 Bugs of the new AST > > compiler", that in my humble opinion absolutely needs to be fixed before > > the release, even though I won't hide that I have no intention of fixing > > it myself. Should I raise the issue here in python-dev, and see if we > > agree that it is critical? > > > > (Sorry if I should know about the procedure. Does it then go in the > > PEP's Planned Features list?) > > > > > > A bientot, > > > > Armin > > _______________________________________________ > > Python-Dev mailing list > > Python-Dev@python.org > > http://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: > > http://mail.python.org/mailman/options/python-dev/jeremy%40alum.mit.edu > > > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
