On Tue, Apr 09, 2002, M.-A. Lemburg wrote: > > I wouldn't want to get c.l.p style discussions on python-dev about > PEPs, though. Why not setup a special PEP discussion list and then > invite people from c.l.p over to it for additional insights ? > > Regarding the subject line: don't know if it's just me, but I > would like to see some of the conservative development style we > had established a few years ago return in Python's development > process. Some of the recent developments left me under the impression > of the need to rush changes with no apparent reason (for rushing > them). Or, to put it another way, perhaps before development work for each release starts (aside from bug fixes), we draw up a list of the feature goals for that release and project a target date for finishing those goals, but the goals get the focus rather than the date. Changing goals after development starts would require official BDFL prounouncement. If a great feature comes up after development starts, too bad -- the next development cycle will usually be less than nine months away. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "There are times when effort is important and necessary, but this should not be taken as any kind of moral imperative." --jdecker
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