Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2001-September/017661.html below:

[Python-Dev] Integrating Expat

• Previous message: [Python-Dev] Python 2.2a* getattr suggestion and question
• Next message: [Python-Dev] Integrating Expat
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[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.

Regards,
Martin

• Previous message: [Python-Dev] Python 2.2a* getattr suggestion and question
• Next message: [Python-Dev] Integrating Expat
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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