[issue25133] Clarify that the constants in selectors are module-level

[Roundup Robot]

Roundup Robot added the comment:

New changeset f03c074b6242 by Brett Cannon in branch 'default':
Merge for issue #25133
https://hg.python.org/cpython/rev/f03c074b6242

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25133] Clarify that the constants in selectors are module-level

[Brett Cannon]

Brett Cannon added the comment:

Changeset 8054a9f788e7 has the 3.5 change.

--
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25133] Clarify that the constants in selectors are module-level

[Brett Cannon]

New submission from Brett Cannon:

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".

--
assignee: brett.cannon
components: Documentation
keywords: easy
messages: 250792
nosy: brett.cannon
priority: low
severity: normal
stage: needs patch
status: open
title: Clarify that the constants in selectors are module-level
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com