[issue25257] In subject line email library inserts unwanted space after a thousands comma in a number

2018-03-27 Thread Bob Hossley
Bob Hossley <bhoss...@ieee.org> added the comment: Mike, Thank you. I moved to Python 3 some time ago. I confirm that Python 3 does not have the problem. But I can't conveniently verify your workaround for Python 2. Regards, Bob bhoss...@ieee.org On 2018-03-27 11:30 AM, Mike Edmunds

[issue25257] In subject line email library inserts unwanted space after a thousands comma in a number

2015-09-28 Thread Bob Hossley
New submission from Bob Hossley: In my function makeMsg(), there is: msg = email.mime.nonmultipart.MIMENonMultipart('text', 'plain', charset='utf-8') msg['Subject'] = email.header.Header(subject, 'utf-8') subject has no space after the thousands comma: u'1,010 words

[issue25257] In subject line email library inserts unwanted space after a thousands comma in a number

2015-09-28 Thread Bob Hossley
Bob Hossley added the comment: Thank you R. David Murray. I look forward to being able to move my application to Python 3. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue24949] Identifier lookup in a multi-level package is flakey

2015-08-31 Thread Bob Hossley
Bob Hossley added the comment: msg<249269> Thank you David Murray. I should have asked myself, what is reasonable behavior? In the case of email.mime.nonmultipart an explicit import is clearly needed. I was misled by my experience with the os library. As a "package" it is

[issue24949] Identifier lookup in a multi-level package is flakey

2015-08-31 Thread Bob Hossley
Bob Hossley added the comment: msg249272 Thank you Martin Panter for the documentation URL's. The import machinery is so complicated that I have given up trying to understand what is "correct" behavior.Depending on the code in the relevant __init__.py and/or explicitly referen

[issue24949] Identifier lookup in a multi-level package is flakey

2015-08-27 Thread Bob Hossley
New submission from Bob Hossley: This seems like a bug to me, but it may be a recognized limitation even though I couldn't find any documentation suggesting that my tests should not work reliably. I see no reason why my tests should not work reliably. I have reliably reproduced