Message 357604 - Python tracker

➜

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	methane
Recipients	James Hennessy, graham.coster, martin.panter, methane, miss-islington, r.david.murray, serhiy.storchaka, xtreak
Date	2019-11-28.06:04:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1574921064.15.0.198337428698.issue26730@roundup.psfhosted.org>
In-reply-to

Content
> Do we need to explicitly document the return value change of _file which is documented with a separate versionchanged directive for 3.7 and 3.8? I feel it is too detailed. Note that the _file attribute may be TextIOWrapper after rollover() anyway and the rollover() may be called implicitly. The code depending on the specific type of the _file is fragile at first.

> Do we need to explicitly document the return value change of _file which is documented with a separate versionchanged directive for 3.7 and 3.8?

I feel it is too detailed.

Note that the _file attribute may be TextIOWrapper after rollover() anyway and the rollover() may be called implicitly.
The code depending on the specific type of the _file is fragile at first.

History
Date	User	Action	Args
2019-11-28 06:04:24	methane	set	recipients: + methane, r.david.murray, martin.panter, serhiy.storchaka, James Hennessy, miss-islington, xtreak, graham.coster
2019-11-28 06:04:24	methane	set	messageid: <1574921064.15.0.198337428698.issue26730@roundup.psfhosted.org>
2019-11-28 06:04:24	methane	link	issue26730 messages
2019-11-28 06:04:23	methane	create