Home Original page

Splitting c.l.py...

Neil Hodgson neilh at scintilla.org
Fri Jul 7 23:52:44 EDT 2000 
> Beats me.  Hmm... here's a possibility: ...  Essentially the newsgroup
would
> be a read-only view of the python-dev mailing list.

   But would it be of interest to anyone? python-dev has a much worse
signal-to-noise ratio than comp.lang.python IMHO. One morning this week I
opened up my mailer in the morning to see over 100 messages in python-dev
and less than 80 in c.l.py.

   The traffic in python-dev alternates between checkin chat (there's a CVS
lock here,  that patch breaks on X, when will you finish Y?) and
language/library design issues. I can see a reason for some of the detailed
design issues to be decided on the same forum as the checkin chat with a
limited group of people, but some of the larger issues should be debated in
a wider forum. Was there any reason for "urllib.browse() issues" to be on
python-dev?

   Possibly comp.lang.python is also a bad forum for discussing future
changes to Python and should concentrate on solving peoples current problems
and avoiding long winded discussions on new functionality. So a
comp.lang.python.future (or similar mailing list) could provide a way for
/all/ Pythoneers to be involved in the evolution of the language.

   Neil
More information about the Python-list mailing list