Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2013-03-09 16:52:11 →
Size: 3646
Editor: RurpyDeprado
Comment: add info about "old" GG interface.
← Revision 3 as of 2013-10-28 03:37:45 → ⇥
Size: 3952
Editor: RurpyDeprado
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Many people find reading the comp.lang.python newsgroup / python-list mailing list on [[https://groups.google.com/forum/#!forum/comp.lang.python|Google Groups]] to be simple and convenient. It is also possible to post messages to the list from there. However, messages sent from Google Groups have some problems that some readers of the Python list would appreciate if you fix before clicking the Post button.
Line 4: Line 5:
In addition to reading the comp.lang.python newsgroup / python-list mailing list on Google Groups, it is also possible to post to the group/list from Google Groups.


However there are some problems you should be aware of before clicking the Post button.


1. Google groups may post your message twice.


 . When you compose a new message or reply in Google Groups, you will sometimes see a checkbox above the post compose window that says:
 Cc: pytho...@python.org

 '''Please uncheck this box before sending!''' If you don't your message will be sent to both the Python list and the Python newsgroup and, since the two are gatewayed together (each receives a copy of anything sent to the other), everyone will see two copies of your post.



2. When you compose a reply to a message, Google Groups adds an excessive number of quoted blank lines.


 . For example, if you reply to a message that already contains some quoted text like this:		 1. '''Please remove extra blank ">" lines.'''
 . When you reply to a message Google Groups includes the message you are replying to prefixed (aka "quoted") with ">" characters. This context helps the reader of your reply understand what the discussion is about. The problem is that Google Groups adds a number of empty lines with nothing but ">" characters. For example:
Line 25: Line 8:
>
Line 28: Line 12:
>
> The code is at http://somewhere/strange
}}}
 the quoted text that Google inserts into the post compose window and which you will see will look like this:
 {{{
>
> > When I changed it so that it said class Foo(object) it gave me
>
> >
>
> > a traceback error when printing out the results. Any ideas?
Line 45: Line 18:
 Every additional level of quoting results in Google Groups adding additional quoted blank lines. Reading a message formatted this way is annoying and many readers will simply ignore it.
 You should '''remove the excess quoted blank lines''' before posting. There are several way to do this.
Line 48: Line 19:
  1. If the quoted text is short, just removed the excess quoted blank lines by hand. (Proper netiquette requires you to remove parts of the quoted text that aren't necessary for context anyway.)  Reading a message formatted this way is annoying and many readers will ignore it or complain about it.
 You should remove the excess quoted blank lines before posting. There are several way to do this.

 1. If the quoted text is short, just removed the excess quoted blank lines by hand. (Proper netiquette requires you to remove parts of the quoted text that aren't relevant to your reply anyway which will lessen what you need to fix.)
Line 53: Line 27:
 What you should not do is not provide any quoted text at all -- in a moderate to high-volume group, context is very important to readers of your email who may have long since forgotten the message you are replying to.
Line 55: Line 28:
 However you do it, the context lines above should end up looking something like:
 {{{
> When I changed it so that it said class Foo(object) it gave me
> a traceback error when printing out the results. Any ideas?
>
> > The code is at http://somewhere/strange
 }}}
 Please do not simply remove all the context -- in a moderate to high-volume group, context is very important to readers of your post who may have long since forgotten the message you are replying to.
Line 56: Line 37:
3. Not all list readers may see your post. 2. '''Please don't remove attributions.'''
 . Attributions are at the top of the context lines and say who posted the message(s) you are replying to. They look like:
 {{{
On Saturday, October 26, 2013 7:02:19 AM UTC-6, Ben Finney wrote:
> On Saturday, October 26, 2013 10:33:10 PM UTC-6, ru...@yahoo.com wrote:
 }}}
Line 58: Line 44:
3. '''Not all list readers may see your post.'''
 . Because of the above problems, the amount of spam posted via Google Groups and other reasons, there are some regular and knowledgeable list participants that filter out posts made from Google Groups. It is not clear that more than a few people do this and most posters from Google Groups get good responses. If you want every possible person to see your post you may want to try posting using one of the other methods described in [[CompLangPython|CompLangPython]].
Line 59: Line 47:
 . Because of the above problems, the amount of spam posted via Google Groups and other reasons, there are some regular and knowledgeable list participants that filter out and ignore posts made from Google Groups. It is not clear how many people do this, and most posters from Google Groups get good responses, but there are some. If you want every possible person to see your post, or you have not received any good answers (or possibly any answers) to your question, you may want to try posting to the list using one of the other methods described in
 [[CompLangPython|CompLangPython]].		 4.''' Follow accepted mailing list netequitte.''' These are conventions that all posters should try to follow, they are not specific to Google Groups posters. See for example http://en.wikipedia.org/wiki/Etiquette_%28technology%29#Netiquette. Two often complained about when ignored are:
Line 62: Line 49:
Another way to avoid the above problems is to use the "old" Google Groups interface. See this Python mailing list
post for instructions on switching to the old interface: http://mail.python.org/pipermail/python-list/2012-October/633460.html		  * Please don't top post. Either put your reply text below any context text, not above it, or interleave your reply text within the context text by inserting each part of your reply immediately below the particular part of the context text to which it applies.

 * Remove (trim) context that is not relervant to your reply.

Posting from Google Groups

Many people find reading the comp.lang.python newsgroup / python-list mailing list on Google Groups to be simple and convenient. It is also possible to post messages to the list from there. However, messages sent from Google Groups have some problems that some readers of the Python list would appreciate if you fix before clicking the Post button.

1. Please remove extra blank ">" lines.

  • When you reply to a message Google Groups includes the message you are replying to prefixed (aka "quoted") with ">" characters. This context helps the reader of your reply understand what the discussion is about. The problem is that Google Groups adds a number of empty lines with nothing but ">" characters. For example: 

    >
> When I changed it so that it said class Foo(object) it gave me
>
> a traceback error when printing out the results. Any ideas?
>
> >
>
> > The code is at http://somewhere/strange
>
    Reading a message formatted this way is annoying and many readers will ignore it or complain about it. You should remove the excess quoted blank lines before posting. There are several way to do this.
    1. If the quoted text is short, just removed the excess quoted blank lines by hand. (Proper netiquette requires you to remove parts of the quoted text that aren't relevant to your reply anyway which will lessen what you need to fix.)
    2. Open a New Mail Message compose window in your favorite email program. Then copy the text of the original message (not the screwed up quoted message in the Google Groups compose window) and use your email program's "Paste as quotation" function to paste into the email window. You can then copy and paste the properly quoted message back into the Google Groups post window.
    3. Do the same as above but with your favorite text editor program and use your editor's Replace function to add the quote markers yourself.
    However you do it, the context lines above should end up looking something like: 
    > When I changed it so that it said class Foo(object) it gave me
> a traceback error when printing out the results. Any ideas?
>
> > The code is at http://somewhere/strange
    Please do not simply remove all the context -- in a moderate to high-volume group, context is very important to readers of your post who may have long since forgotten the message you are replying to.

2. Please don't remove attributions.

  • Attributions are at the top of the context lines and say who posted the message(s) you are replying to. They look like: 
    On Saturday, October 26, 2013 7:02:19 AM UTC-6, Ben Finney wrote:
> On Saturday, October 26, 2013 10:33:10 PM UTC-6, ru...@yahoo.com wrote:

3. Not all list readers may see your post.

  • Because of the above problems, the amount of spam posted via Google Groups and other reasons, there are some regular and knowledgeable list participants that filter out posts made from Google Groups. It is not clear that more than a few people do this and most posters from Google Groups get good responses. If you want every possible person to see your post you may want to try posting using one of the other methods described in CompLangPython.

4. Follow accepted mailing list netequitte. These are conventions that all posters should try to follow, they are not specific to Google Groups posters. See for example http://en.wikipedia.org/wiki/Etiquette_%28technology%29#Netiquette. Two often complained about when ignored are:

  • Please don't top post. Either put your reply text below any context text, not above it, or interleave your reply text within the context text by inserting each part of your reply immediately below the particular part of the context text to which it applies.
  • Remove (trim) context that is not relervant to your reply.

GoogleGroupsPython (last edited 2014-02-12 22:05:20 by MarcAndreLemburg)

Unable to edit the page? See the FrontPage for instructions.