Message27607
| Author |
skip.montanaro |
| Recipients |
| Date |
2006年02月23日.23:59:34 |
| SpamBayes Score |
| Marked as misclassified |
| Message-id |
| In-reply-to |
| Content |
This may apply to the trunk as well...
Today I finished installing 2.4.2 and all our local libraries at work.
Trying out the main application I use I discovered Python segfaulting
when trying to import pyexpat. It turned out that during the import
an earlier module (gtk.glade) also wanted libexpat. Apparently pyexpat
was expecting to get Expat 1.95.8 (what's delivered with Python) but
got 1.95.7 instead (what we had installed and what was already linked
with all our other Expat-using code).
The solution was rather simple. I just commented out those constants
in the pyexpat initialization that were marked as 1.95.8. Fortunately
there was a comment identifying the version dependency.
Is there some way that Python's build process can detect the Expat
version and conditionally include/exclude bits that are for later
versions?
|
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2007年08月23日 14:38:03 | admin | link | issue1437785 messages |
| 2007年08月23日 14:38:03 | admin | create |
|