Message 120179 - Python tracker

➜

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	eric.araujo, jelie, r.david.murray
Date	2010-11-01.21:28:28
SpamBayes Score	5.0809747e-05
Marked as misclassified	No
Message-id	<1288646909.66.0.445791226319.issue10284@psf.upfronthosting.co.za>
In-reply-to

Content
Éric: there is no notion of encoding in a few NNTP commands. Regarding AUTHINFO, the real string that I should have written is: AUTHINFO USER \xC9ric 7-bit bytes are considered to be encoded in ASCII. 8-bit bytes are just 8-bit bytes. No encoding. The news client and the news server have to agree on the setting. Authentification occurs between them. I can imagine the news client in ISO-8859-1 and the news server in ISO-8859-15, and a password with a « € » sign in. Then the password will not be the "same" (when entered on the keyboard), but will match in bytes! I hope my explanation was clear enough now. No encoding, just byte strings here!

Éric:  there is no notion of encoding in a few NNTP commands.
Regarding AUTHINFO, the real string that I should have written is:

AUTHINFO USER \xC9ric

7-bit bytes are considered to be encoded in ASCII.
8-bit bytes are just 8-bit bytes.  No encoding.

The news client and the news server have to agree on the setting.  Authentification occurs between them.
I can imagine the news client in ISO-8859-1 and the news server in ISO-8859-15, and a password with a « € » sign in.  Then the password will not be the "same" (when entered on the keyboard), but will match in bytes!


I hope my explanation was clear enough now.
No encoding, just byte strings here!

History
Date	User	Action	Args
2010-11-01 21:28:29	jelie	set	recipients: + jelie, eric.araujo, r.david.murray
2010-11-01 21:28:29	jelie	set	messageid: <1288646909.66.0.445791226319.issue10284@psf.upfronthosting.co.za>
2010-11-01 21:28:28	jelie	link	issue10284 messages
2010-11-01 21:28:28	jelie	create