> As for process issues...I agree that we need better procedures and criteria
> for what goes into the library.
For a start, my current understanding is:
- Adding a module to the standard library is a big change.
- Modifying a core type or the interpreter loop is a big change.
- Breaking compatibility is a big change.
- Any big change requires confirmation specifically from Guido.
I was pretty surprised to see compilerlike.py go in. Even if i had
seen +1s from everyone else on python-dev, i still wouldn't have
been comfortable checking it in without hearing from the BDFL.
-- ?!ng
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