Thomas Wouters <thomas@xs4all.net>: > That depends on what the PEP does. PEPs can do two things (according to the > PEP that covers PEPs :): argue for a new feature/addition to the Python > language, or describe a standard or procedure of some sort. This PEP could > perhaps do both: describe a standard procedure for proposing and accepting a > new module in the library (and probably also removal, though that's a lot > trickier) AND do some catching-up on that process to get a few good modules > into the stdlib before 2.0 goes into a feature freeze (which is next week, > by the way.) > > As for the procedure to add a new module, I think someone volunteering to > 'adopt' the module and perhaps a few people reviewing it would about do it, > for the average module. Giving people a chance to say 'no!' of course. Sounds like my cue to write a PEP. What's the URL for the PEP on PEPs again? -- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a> See, when the GOVERNMENT spends money, it creates jobs; whereas when the money is left in the hands of TAXPAYERS, God only knows what they do with it. Bake it into pies, probably. Anything to avoid creating jobs. -- Dave Barry
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