> > If the portability problem can be solved by checking things into Jython > > instead, I think I would prefer that. I'm definitely interested in bringing ElementTree into Jython at some point, though I probably won't have time to look into it until after the next Jython release. I'm quite sure that we can work something out so that Jython-specific portability code can reside in Jython only. Though whenever it is cleanly do-able, I'd like to be able to use the python libraries unchanged. It sounds like this is a case where it is not that clean to do... -Frank
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4