On Tue, Mar 22, 2011 at 03:42:27PM -0700, Glenn Linderman wrote: > and didn't figure I had time to learn both. I haven't read the new devguide > yet, but from the activity on the list, it would seem that either no one else I think, it is a good idea to read that. You might find that many discussions are stemming from assumptions rather than following the instructions. > the devguide, and attempt to submit code to the http.server to try to fix the > many bugs and limitations it has, many of which I've worked around or fixed in > a private copy of server.py. No one else seemed to be interested enough in > those bugs when I reported them to fix them prior to the release 3.2, so it I remember your issues, many of them are I would say 'tricky' ones which would need some time to review/fix. Let's see it to get it in 3.3 release. > seems to me that code is basically unmaintained. The present state of the code > is sort of like a dead battery... it might function a little but has such > severe limits that it is not particularly useful... and it is an itch I might > be able to scratch. If you wish, please maintain a mecurial repository and point the full code in the bug-reports, it may be easy to pull a patch and patch the current line of code. -- Senthil
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