> >One question is how spin this. Listing a long series of > >incompatibilities presents the image of a language that has many > >gratuitous incompatible changes -- which is not true and the opposite > >of the message we want to convey. > > This way madness lies. Document nothing and there will certainly be > complaints. Why worry about losers who are in essence complaining > that the documentation is *too* complete? All I'm asking is a leading paragraph something like this: """While the Python developers do their best to make every subsequent release backwards compatible with previous releases, in a system of this complexity, sometimes incompatibilities in odd corners of the language are unavoidable. While we expect that these will affect only a small minority of Python users, we document them here for completeness.""" --Guido van Rossum (home page: http://www.python.org/~guido/)
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