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 steven.daprano
Recipients gregory.p.smith, mbussonn, pablogsal, remi.lapeyre, rhettinger, serhiy.storchaka, steven.daprano
Date 2019-05-20.18:11:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20190520181116.GG4221@ando.pearwood.info>
In-reply-to <1558370571.06.0.805831845594.issue36906@roundup.psfhosted.org>
Content
> While the string method works pretty well, I do not think this is the best way.

Regardless of what we do for literals, a dedent() method will help for 
non-literals, so I think that this feature should go in even if we 
intend to change the default behaviour in the future:

> 3.9. Implement "from __future__ import deindent".
> 3.11. Emit a FutureWarning for multiline literals that will be changed by dedending if "from __future__ import deindent" is not specified.
> 3.13. Make it the default behavior.

And that gives us plenty of time to decide whether or not making it the 
default, rather than an explicit choice, is the right thing to do.
History
Date User Action Args
2019-05-20 18:11:23steven.dapranosetrecipients: + steven.daprano, rhettinger, gregory.p.smith, serhiy.storchaka, mbussonn, pablogsal, remi.lapeyre
2019-05-20 18:11:23steven.dapranolinkissue36906 messages
2019-05-20 18:11:23steven.dapranocreate