Martin von Loewis wrote: > > [I know I've asked this before, but Fred wanted me to ask it again :-] > > What do you think about an integration of Expat into Python, to be > always able to build pyexpat (and with the same version also)? > Which version of Expat would you use? Would you put the expat files > into a separate directory, or all into modules? > > Here is my proposal: Integrate Expat 2.95.2 for release together with > Python 2.2; into an expat subdirectory of Modules (taking only the lib > files of expat). > > This would affect build procedures on all targets; in particular, > pyexpat would not link to a shared expat DLL, but incorporate the > object files. Are you sure that we should choose expat as "native" XML parser ? There are other candidates which would fit this role just as well (in particular, Fredrik's sgmlop looks like a nice extension since it not only works with XML but also many other meta languages). If you want a very fast validating XML parser, RXP would also be a good choice -- AFAIK, the RXP folks would allow us to ship RXP under a different license than GPL which is then bound to Python. Given the many alternatives, I am not sure whether going with expat is the right path... may be wrong though. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
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