Issue 1015140: "article id" in description of NNTP objects (original) (raw)

Issue1015140

Created on 2004-08-24 10:26 by felixwiemann, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg22199 - (view)	Author: Felix Wiemann (felixwiemann)	Date: 2004-08-24 10:26
lib/nntp-objects.html uses the term "article id" several times. This term is ambiguous though. Either "article number" or "message id" should be used.
msg22200 - (view)	Author: Felix Wiemann (felixwiemann)	Date: 2004-08-29 08:11
Logged In: YES user_id=1014490 Same problem for the docstrings in the source file Lib/nntplib.py.
msg22201 - (view)	Author: Raymond Hettinger (rhettinger) *	Date: 2004-08-29 08:20
Logged In: YES user_id=80475 Patches are welcome. If you have a link to authoritive guidance, that would be nice also.
msg22202 - (view)	Author: Felix Wiemann (felixwiemann)	Date: 2004-08-30 20:13
Logged In: YES user_id=1014490 > Patches are welcome. I don't have enough time (and I don't care enough) to write a patch for this, currently. > If you have a link to authoritive > guidance, that would be nice also. The only occurence of the case-insensitive regex 'article.id' in all RFCs is in RFC 977, which says: 223 n a article retrieved - request text separately (n = article number, a = unique article id) (Here, it probably means message-id.) There are frequent occurences of 'article number' and 'message-id' in the NNTP related RFCs 977 and 2980. So 'article id' probably should be avoided, as it is ambiguous. (The docs sometimes use it in the sense of 'message-id' and sometimes as 'article number', from what I could see.)
msg22203 - (view)	Author: Georg Brandl (georg.brandl) *	Date: 2005-07-17 20:27
Logged In: YES user_id=1188172 Corrected in docs and docstrings as Lib/nntplib.py r1.40, r1.39.2.1 Doc/lib/libnntplib.tex r1.33, r1.32.2.1