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 benjamin.peterson
Recipients Mark.Shannon, benjamin.peterson, flherne, georg.brandl, lukasz.langa, methane, ned.deily, rhettinger, serhiy.storchaka, vstinner
Date 2018-05-25.03:15:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527218119.15.0.682650639539.issue32911@psf.upfronthosting.co.za>
In-reply-to
Content
Regardless of the value of .docstring change, it seems it had some unexpected consequences. I think providing a new mode for compile mulitline statements is a reasonable way to address those consequences going forward. That said, it's extremely late in the lifecycle of 3.7 to be thinking about new APIs. How about rolling back the whole .docstring change for 3.7? Then, it can be landed again with compile(..., mode='multiline) for 3.8.
History
Date User Action Args
2018-05-25 03:15:19benjamin.petersonsetrecipients: + benjamin.peterson, georg.brandl, rhettinger, vstinner, ned.deily, methane, lukasz.langa, Mark.Shannon, serhiy.storchaka, flherne
2018-05-25 03:15:19benjamin.petersonsetmessageid: <1527218119.15.0.682650639539.issue32911@psf.upfronthosting.co.za>
2018-05-25 03:15:19benjamin.petersonlinkissue32911 messages
2018-05-25 03:15:18benjamin.petersoncreate