➜

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 scoder
Recipients eli.bendersky, flox, jcea, pitrou, python-dev, scoder
Date 2013-08-23.21:28:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377293319.3.0.297773094999.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content 
Could we please keep the discussion on rational terms?

It's not just the method names. The problem is that you are duplicating an existing class (the XMLParser) for no good reason, instead of putting the feature where it belongs: *behind* the XMLParser. Even worse, you are duplicating the class and giving it a *different* API.

This goes completely against the design of the existing API and counters the reusability of the existing code.

I'm not questioning that the feature is desirable. I'm saying that the design is wrong.
History
Date User Action Args
2013-08-23 21:28:39scodersetrecipients: + scoder, jcea, pitrou, eli.bendersky, flox, python-dev
2013-08-23 21:28:39scodersetmessageid: <1377293319.3.0.297773094999.issue17741@psf.upfronthosting.co.za>
2013-08-23 21:28:39scoderlinkissue17741 messages
2013-08-23 21:28:39scodercreate