Jim Fulton bumped into a gross problem in the 2.1b2 asynchat.py today,
introduced by conversion to string methods (one change got the order of
.find() arguments backwards).
This is embarrassing (or should be <wink>), because it meant asynchat.py
really had no chance of working at all! And if Jim hadn't bumped into it, we
would have shipped it this way for 2.1 final next week.
I haven't used those modules myself, so don't know whether this request is
reasonable: could someone please whip up an at least minimal standard test
case for these modules? So long as it runs on at least one of {Windows,
Linux}, we'd catch problems like this almost instantly. As is, AFAICT we
don't even import asynchat (the "import asynchat" line in test_sundry.py is
commented out but no reason is given for that -- anyone know why?).
don't-everyone-volunteer-at-once-ly y'rs - tim
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