> I am aware of the situation with regard to issue reviews, but I think > with IDLE there is more going on. In other parts of the Python > codebase, a workaround for a major usability issue wouldn't normally > have taken nearly three years to resolve after a working patch was > submitted. Oh sure it does. Just look at all the cross-compilation bug reports and patches that get submitted. > And a working, well-tested patch wouldn't normally have sat > ignored for over two years. Well, perhaps these things happen > occasionally, but with IDLE this is the norm. Unfortunately, they happen more often than you think. Regards, Martin
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