This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jelie
Recipients jelie
Date 2010-11-01.19:53:13
SpamBayes Score 1.5317559e-05
Marked as misclassified No
Message-id <1288641195.29.0.702249344241.issue10280@psf.upfronthosting.co.za>
In-reply-to
Content
The NNTP version is currently defined as follows in the source code:

self.nntp_version = int(caps['VERSION'][0])

However, Section 3.3.2 of RFC 3977 mentions:

   VERSION
      This capability MUST be advertised by all servers and MUST be the
      first capability in the capability list; it indicates the
      version(s) of NNTP that the server supports.  There must be at
      least one argument; each argument is a decimal number and MUST NOT
      have a leading zero.  Version numbers are assigned only in RFCs
      that update or replace this specification; servers MUST NOT create
      their own version numbers.

There can be more than one version.
See the example in Section 5.2.3:

      [S] VERSION 2 3

I believe the best thing to do would be to take the max of the numbers, that is to say:

self.nntp_version = max(map(int, caps['VERSION']))
History
Date User Action Args
2010-11-01 19:53:15jeliesetrecipients: + jelie
2010-11-01 19:53:15jeliesetmessageid: <1288641195.29.0.702249344241.issue10280@psf.upfronthosting.co.za>
2010-11-01 19:53:13jelielinkissue10280 messages
2010-11-01 19:53:13jeliecreate