Mailman 3 January 2012 - docs

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by R. David Murray Jan. 3, 2012

Jan. 3, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: Would you be interested in providing a patch that includes tests? I think Antoine set up a test framework for testing the login as part of issue 4471. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13700> _______________________________________

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by Erno Tukia Jan. 3, 2012

Jan. 3, 2012

Erno Tukia <erno.tukia(a)iki.fi> added the comment: I tried to fix the problem and the correct fix is to change oup = '' to oup = b'' in imaplib._Authenticator.encode() function, and not what I suggested in my previous post. After changing that PLAIN authentication works. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13700> _______________________________________

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by Erno Tukia Jan. 3, 2012

Jan. 3, 2012

Erno Tukia <erno.tukia(a)iki.fi> added the comment: In Python 2.6 PLAIN authentication works, in Python 3.1 not. Lib/test/test_imaplib.py does not test IMAP4.authenticate() or IMAP4.login_cram_md5() functions, only IMAP4.login(). I would still like to go back to imaplib._Authenticator.encode() function. The function is below. # inp = authobject(response) def encode(self, inp): oup = '' while inp: if len(inp) > 48: t = inp[:48] inp = inp[48:] … [View More]

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by R. David Murray Jan. 3, 2012

Jan. 3, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: Bytes definitely. We hashed that out a while ago. My point is that CRAM_MD5 login calls authenticate, and its authenticator returns a string, just like your example does. So it ought to be going through the same code path. I haven't followed the logic in detail, though, so there must be some difference...I'm pretty sure the MD5 login has a test now (but not 100% sure...) ---------- _______________________________________ … [View More]

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by Erno Tukia Jan. 3, 2012

Jan. 3, 2012

Erno Tukia <erno.tukia(a)iki.fi> added the comment: File "/usr/lib/python3.1/imaplib.py", line 1257, in encode e = binascii.b2a_base64(t) imaplib._Authenticator.encode() calls binascii.b2a_base64() function. In Python 2.6 that function returns a string, and in Python 3.1 it returns bytes. What is returned from b2a_base64() function is later in the encode() function concatenated with a string, with bytes that is not possible. Should binascii.b2a_base64() return a string (2.6) or … [View More]

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by R. David Murray Jan. 3, 2012

Jan. 3, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: Gah, I was looking at the wrong source code when I wrote that. A string first argument is indeed valid. I'm not sure where the problem is coming from since the internal CRAM_MD5 returns a string and that seems to work... ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13700> _______________________________________

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by Erno Tukia Jan. 3, 2012

Jan. 3, 2012

Erno Tukia <erno.tukia(a)iki.fi> added the comment: The same problems exists even if I use b"PLAIN" as the first argument in authenticate(). ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13700> _______________________________________

1 0

[issue13700] imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism
by R. David Murray Jan. 3, 2012

Jan. 3, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: The first argument to authenticate must be bytes. This is not well documented. It might also be a bug, since I'm not sure anyone has done a thorough audit of what should be bytes and what should be string in imaplib. 3.1 no longer gets bug fixes, so I'm removing it from versions. Likewise I remove 3.4 since that applies only to changes that will *not* be put in 3.3 for some reason. ---------- assignee: -> docs@python … [View More]

1 0

[issue13685] argparse does not sanitize help strings for % signs
by Eric V. Smith Jan. 2, 2012

Jan. 2, 2012

Eric V. Smith <eric(a)trueblade.com> added the comment: In case I wasn't clear, I mean that the help string supports %-formatting variable expansion, such as "%(default)s". I think it would be good if a sentence were added to the end of the "help" section, saying something like: Because the help string supports %-formatting, if you want a literal "%" to appear in the help string, you must escape it as "%%". ---------- _______________________________________ Python tracker <report(a)… [View More]

1 0

[issue13690] Add DEBUG flag to documentation of re.compile
by Éric Araujo Jan. 2, 2012

Jan. 2, 2012

Éric Araujo <merwok(a)netwok.org> added the comment: > Display debug information about compiled expression. IMO it would be helpful to define “display” more precisely (e.g. “Print debugging information on stdout during pattern compilation”). ---------- nosy: +eric.araujo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13690> _______________________________________

1 0