> I've finally checked my string methods changes into the source tree, > albeit on a CVS branch (see below). These changes are outgrowths of Yay! Would this also be a good opportunity to dust-off the Unicode implementation the string-sig recently came up with (as implemented by Fredrik) and get this in as a type? Although we still have the unresolved issue of how to use PyArg_ParseTuple etc to convert to/from Unicode and 8bit, it would still be nice to have Unicode and String objects capable of being used interchangably at the Python level. Of course, the big problem with attempting to test out these sorts of changes is that you must do so in code that will never see the public for a good 12 months. I suppose a 1.5.25 is out of the question ;-) Mark.
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