c.l.py.{help,future,library,language,misc,advocacy,gui,platform-dependent,moderated,ternary,peps,whining,flamewar,timbot,obfuscated,goto}

Greg Ewing (using news.cis.dfn.de) me at privacy.net
Mon Feb 10 23:02:30 EST 2003


Gerrit Holl wrote:

> possible options are:
> 
> 	* c.l.py.help
> 	* c.l.py.future
> 	* c.l.py.library
> 	* c.l.py.language
> 	* c.l.py.misc
> 	* c.l.py.advocacy
> 	* c.l.py.gui
> 	* c.l.py.platform-dependant
> 	* c.l.py.moderated


Please, no. I've seen this sort of split done before (e.g.
comp.sys.mac) and it doesn't really work. It's often unclear
which sub-group a message belongs in, or it clearly belongs
in more than one sub-group, so you end up with huge amounts
of cross-posting.

Leave the group the way it is, and get used to using the
"Mark thread as read" command! (And if your newsreader
doesn't have one, get one that does.)

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg





More information about the Python-list mailing list