Home Original page

Splitting comp.lang.python

rmeegan at murlmail.com rmeegan at murlmail.com
Wed Mar 1 09:07:53 EST 2000 
Greetings -

I find it very hard to seperate the technical and non-technical aspects 
of c.l.py. For example, are newbie questions technical? What if the 
response brings up a technical aspect? Does the thread somehow move to 
the correct newsgroup? 

In what Tim would surely rate as no more than a <0.5 wink>, I propose 
that a more useful split would be to create a seperate newsgroup for 
messages that advocate the end of whitespace for block delimiting and 
the addition of functional programming features, along with John 
Skaller's explanations of the superiority of Viper (Vyper?) to Python. 
This split alone should remove roughly 42% of the postings in any given 
month. 

Your humble servant,
- Robert

> Hello,
> 
> Quoting Fredrik Lundh <effbot at telia.com>,
> > this month, comp.lang.python has seen nearly
> > 50% more posts than any month before:
> > 
> >     http://www.egroups.com/group/python-list/info.html
> >     http://starship.python.net/crew/just/FindMailStats/
> 
> 4000 messages in 29 days is a lot. it's 138 messages a day. Previous
> discussions on splitting c.l.py always ended up in jokes and just
> disappeared; I want to resurrect an informal discussion on wheter
> to split the newsgroup or not; an RFD should be posted, of course,
> but IANAL: does anyone have time to create an RFD?
> 
>     I propose to split c.l.py in a technical part and a non-technical 
part. 
> 
> regards,
> Gerrit.
> 
> -- 
> Comparison Python GUI's: http://www.nl.linux.org/~gerrit/gui.html
> Please comment!
> 
> -- 
> http://www.python.org/mailman/listinfo/python-list
More information about the Python-list mailing list