[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-09-08 Thread R. David Murray
R. David Murray added the comment: Cleaned up the code. It was basically working by accident with the misspelling. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-09-08 Thread Roundup Robot
Roundup Robot added the comment: New changeset 468961cea562 by R David Murray in branch '3.5': #27630: Be consistent in how _XXX/_encoded_XXX vars are initialized. https://hg.python.org/cpython/rev/468961cea562 New changeset ddb1cf7b7eb1 by R David Murray in branch 'default': Merge: #27630: Be

[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-08-31 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> r.david.murray ___ Python tracker ___

[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-08-30 Thread Martin Panter
Martin Panter added the comment: FYI in 3.6 the spelling has been changed to _EMPTY (Issue 27895) -- ___ Python tracker ___

[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-07-27 Thread R. David Murray
R. David Murray added the comment: The former is kept (IIRC) for backward compatibility, the latter should be investigated. Since I wrote that code I'll have to add this to my todo list. -- ___ Python tracker

[issue27630] Generator._encoded_EMTPY misspelling in email package

2016-07-26 Thread Martin Panter
New submission from Martin Panter: In the Generator.flatten() (Lib/email/generator.py), the code sets, among others, the instance attributes _EMPTY (correct spelling) and _encoded_EMTPY (misspelling). Further down in that class, _encoded_EMPTY (correct spelling) is set as a class attribute,