➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients Arfrever, effbot, eli.bendersky, ezio.melotti, flox, georg.brandl
Date 2012-02-26.22:18:46
SpamBayes Score 0.0003868701
Marked as misclassified No
Message-id <CAF-Rda8sCgzV+trTrfsU-Q+iFzGFGd89q4BxaoEo13emcGyZ1w@mail.gmail.com>
In-reply-to <1330292977.62.0.217634762569.issue14007@psf.upfronthosting.co.za>
Content 
On Sun, Feb 26, 2012 at 23:49, Florent Xicluna <report@bugs.python.org>wrote:

Yes, these suggestions sound reasonable to me. Moving toward two more
consistent implementations of the API, while not disabling existing
features is the way to go. Things like relaxing the Python XMLParser just
add features rather than restricting them, so they should not result in
breakage due to backward-incompatibility.

Eli
History
Date User Action Args
2012-02-26 22:18:47eli.benderskysetrecipients: + eli.bendersky, effbot, georg.brandl, ezio.melotti, Arfrever, flox
2012-02-26 22:18:46eli.benderskylinkissue14007 messages
2012-02-26 22:18:46eli.benderskycreate