my 2cts. I think Zope is a bad example, because Zope 2.x is adding features while being developed against 2.1. but Zope 3 is a total rewrite against 2.2 technology. I have the impression that Python is still too young, not strict, and too much reflective and people like to code against the grey area of what I would call implementation details and to avoid reading the docs, that developing (increasing features) only against 2.X and jump to 2.Y (with Y>X) when it becomes "stable", is a bad unpleasant move if the 2.X line will not be here for eternity (and it won't). Unless the whole thing becomes a real (and painful) exercise, in back-porting warnings, and designing transition paths for things that at first sight nobody would have thought they had influence on someone or something. regards.
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