Vladimir Marangozov wrote:
>
> ...
> Why "deprecate"? xmllib is a solution which tends to be replaced by a new one,
> so chances are that in the long run, having pyexpat, development will shift
> to additional XML tools which have more added value than xmllib.
We don't want to encourage programmers to use the old xmllib API. I was
actually one of a minority that said that we should put the xmllib API
on top of expat. Most people said: "don't do that or people will keep
using that API."
The argument for deprecating (not removing) PyExpat goes like this:
* having multiple ways to do the same thing is not the Python way
* the APIs are close enough that moving to SAX should be easy
* SAX is a good marketing buzzword and it makes moving from other
languages easier.
* the xmllib API has a little bit of weird stuff inherited from
sgmllib.
It's basically about causing confusion by offering too many choices.
--
Paul Prescod - ISOGEN Consulting Engineer speaking for himself
"The calculus and the rich body of mathematical analysis to which it
gave rise made modern science possible, but it was the algorithm that
made possible the modern world."
- from "Advent of the Algorithm" David Berlinski
http://www.opengroup.com/mabooks/015/0151003386.shtml
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4