> The policy about beta releases is (or should be) stricter. No new > features, and perhaps no new tests unless they test for a bug that > gets fixed. So in the beta cycle, patches are posted to SF just to > store them there until after the release of Python 2.3. I don't see much of a reason to be so strict about no new tests. > In the specific case, ask yourself what the cost would be if you > produce a test failure under conditions that you consider obscure. > Will enough people test the test before 2.3 is released? Does the new > test suite behave differently enough from the old one to make false > positives a possibility? This is always a good set of questions to ask yourself. --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