Comment 12 for bug 343242
Revision history for this message
| Bruno Harbulot (bruno-harbulot) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hello,
Apologies for restarting the discussion, but I'm still not convinced about the arguments for removing PyXML. (Like others who have commented on this issue, I have some code that depends on PyXML's XPath capabilities; changing to another implementation would require substantial changes.)
I do realise that PyXML has been inactive for a while (the latest file available for download on the SourceForge page dates back from November 2004, which is almost 5 years ago). However, I wonder if this really is an argument for discontinuing its inclusion. Does a project need to have continuous releases to be included? If something is not broken, why fix it?
A good reason for not including it would be that it breaks with some newer versions of Python and that it hasn't been maintained, but perhaps the reason there haven't been any new releases is simply the fact it doesn't need any urgent maintenance (triggered by external changes). Are there any issues that need maintenance because of recent changes in Python?