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.

classification
Title: Clarify that the constants in selectors are module-level
Type: Stage: resolved
Components: Documentation Versions: Python 3.6, Python 3.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: brett.cannon Nosy List: brett.cannon, python-dev
Priority: low Keywords: easy

Created on 2015-09-15 18:34 by brett.cannon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg250792 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2015-09-15 18:34
If you read the docs for the selectors module it isn't obvious that the constants EVENT_WRITE and EVENT_READ are module-level and not on the various classes since they are in the Classes section of the doc. Shouldn't require any more than adding the word "module" to "the constants below".
msg251037 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2015-09-18 22:21
New changeset f03c074b6242 by Brett Cannon in branch 'default':
Merge for issue #25133
https://hg.python.org/cpython/rev/f03c074b6242
msg251038 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2015-09-18 22:22
Changeset 8054a9f788e7 has the 3.5 change.
History
Date User Action Args
2022-04-11 14:58:21adminsetgithub: 69320
2015-09-18 22:22:08brett.cannonsetstatus: open -> closed
resolution: fixed
messages: + msg251038

stage: needs patch -> resolved
2015-09-18 22:21:33python-devsetnosy: + python-dev
messages: + msg251037
2015-09-15 18:34:44brett.cannoncreate