Message28949
Logged In: YES
user_id=3066
I've managed to come up with a patch that solves this
specific issue, but it really deals with the symptom and not
the real problems.
While I think the "xmlcore" package was the right idea, I'm
not convinced it can be correctly implemented without
enormous effort at this time. Given the release schedule,
it doesn't make sense to jump through those hoops. The
previous hackery that made allowed the PyXML distribution to
"replace" the standard library version of the "xml" package
worked only because there was only one public name for
whichever was being used. Moving to the "xmlcore" package
proved to be more than that hack could support.
I think the right thing to do for Python 2.5 is to revert
the changes that added the "xmlcore" package. Further
investigation into a better approach can be made for Python 2.6. |
|
Date |
User |
Action |
Args |
2007-08-23 14:40:52 | admin | link | issue1513611 messages |
2007-08-23 14:40:52 | admin | create | |
|