[Lxml-checkins] r52006 - in lxml/trunk: . doc

scoder at codespeak.net scoder at codespeak.net
Sat Mar 1 17:59:51 CET 2008


Author: scoder
Date: Sat Mar  1 17:59:49 2008
New Revision: 52006

Modified:
   lxml/trunk/   (props changed)
   lxml/trunk/doc/FAQ.txt
Log:
 r3651 at delle:  sbehnel | 2008-03-01 17:00:46 +0100
 clarification on MacOS-X crashes


Modified: lxml/trunk/doc/FAQ.txt
==============================================================================
--- lxml/trunk/doc/FAQ.txt	(original)
+++ lxml/trunk/doc/FAQ.txt	Sat Mar  1 17:59:49 2008
@@ -408,15 +408,15 @@
    the FAQ section on threading_ to check if you touch on one of the
    potential pitfalls.
 
-b) If you are on Mac-OS X, make sure lxml uses the correct libraries.  If you
-   have updated the old system libraries (e.g. through fink), this is best
-   achieved by building lxml statically to prevent the different library
-   versions from interfering.  If you choose to use a dynamically linked
-   version, make sure the ``DYLD_LIBRARY_PATH`` environment variable contains
-   the directory where you installed the libraries.  To make sure the correct
-   libraries are used, print the module level version numbers that
-   ``lxml.etree`` provides from *within* your application rather than relying
-   on what your operating system tells you.
+b) If you are on Mac-OS X, make sure lxml uses the correct libraries.
+   Since the normal system libraries are pretty much outdated, you
+   likely have installed newer versions through a package management
+   system like fink or macports.  In this case, please make sure the
+   ``DYLD_LIBRARY_PATH`` environment variable contains the directory
+   where you installed the libraries.  There are other Python packages
+   that depend on libxml2, so it is up to you to make sure that *all*
+   packages that dynamically load libxml2 load the *same* library
+   version.  Loading conflicting versions *will* lead to a crash.
 
 In any case, try to reproduce the problem with the latest versions of
 libxml2 and libxslt.  From time to time, bugs and race conditions are found


More information about the lxml-checkins mailing list