Stefan Behnel wrote:
Martin v. Löwis wrote:
I do see the point you are making here. Even if lxml gets mature and
static, that doesn't necessarily apply to the external libraries it uses.
However, I should note that exactly the same argument also applies to
sqlite3 and gdbm, which, again, are in the stdlib today, with sqlite3 being
a fairly recent addition.
Fortunately, it is possible for users to just replace the sqlite DLL in
a Python installation, with no need of recompiling anything.
Interesting. I assume you are referring to Windows here, right? Does that
"just work" because the DLL is in the same directory?
I have no idea, but my WinXP .../Python30/ install has
DLLs/_sqlite3.pyd 52K
DLLs/sqlite3.dll 557K
libs/_sqlite3.lib 2K
For whatever reason, most other things do not have all three files.
I do not know whether upgrades (like 3.0.0 to 3.0.1) would clobber other
things added here.
That would be a nice feature for lxml, too. We could just make the libxml2
and libxslt DLLs package data under Windows in that case.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
