Message315153
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 | edmorley |
|---|---|
| Recipients | docs@python, edmorley |
| Date | 2018-04-09.22:13:44 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1523312024.12.0.682650639539.issue33252@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The `ResourceWarning` warning has always been ignored by default, since it was added in Python 3.2 in: https://github.com/python/cpython/commit/08be72d0aa0112118b79d271479598c218adfd23#diff-db4e2b9efea108a38c53e06fa99cdd77R391 However there are several places in the docs where the "ignored by default" aspect is not mentioned even though it is for `DeprecationWarning` and similar - which caused me quite a bit of confusion today. The docs were partly improved in Python 3.7 onwards by: https://github.com/python/cpython/commit/9b99747386b690007027c3be2a5d7cfe3d3634f5 ...however: (a) there is still at least one place that still needs updating on master (https://docs.python.org/3.8/library/warnings.html#warning-categories) (b) it would be good to backport the docs fixes to 3.4/3.5/3.6 (I was looking at the 3.6 docs today) I'm happy to open PRs to fix this; but filing this issue so I have something to reference. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-04-09 22:13:44 | edmorley | set | recipients: + edmorley, docs@python |
| 2018-04-09 22:13:44 | edmorley | set | messageid: <1523312024.12.0.682650639539.issue33252@psf.upfronthosting.co.za> |
| 2018-04-09 22:13:44 | edmorley | link | issue33252 messages |
| 2018-04-09 22:13:44 | edmorley | create | |