Michael Hudson wrote: > There were a small bundle of bug reports from a guy with libc5 a week > or so back, so there's at least some interest in that. OTOH, I don't > feel like putting all that much effort into fixing the problems he > reported (most of them were failry shallow, I think). So would you propose to "unsupport" Linux with libc 5? By PEP 11 rules, this would become "unsupported" in Python 2.4, with the possibility of revival if a volunteer steps forward. Regards, Martin P.S. I don't like to call this "We deprecate libc5", because we are in no position to decide the future of libc5 (we are not maintaining it in the first place). Instead, we just stop supporting it.
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