It seems to me that the main problem is that comp.lang.python is too big to follow. So why not split it? I don't know the right subgroups, but if (say) comp.lang.python.language focusses on the core language, it might enable people to start reading it again. I asked this twice on c.l.p, one year ago and two years ago, and the answer was always "the traffic is too low". I used to subscribe to the NeXTSteap groups, and splitting worked really well there. - Andy Robinson
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