-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
GH-101100: Resolve reference warnings in library/stdtypes.rst #138420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4755,11 +4755,12 @@ other sequence-like behavior. | |
|
|
||
| There are currently two built-in set types, :class:`set` and :class:`frozenset`. | ||
| The :class:`set` type is mutable --- the contents can be changed using methods | ||
| like :meth:`~set.add` and :meth:`~set.remove`. Since it is mutable, it has no | ||
| hash value and cannot be used as either a dictionary key or as an element of | ||
| another set. The :class:`frozenset` type is immutable and :term:`hashable` --- | ||
| its contents cannot be altered after it is created; it can therefore be used as | ||
| a dictionary key or as an element of another set. | ||
| like :meth:`add <frozenset.add>` and :meth:`remove <frozenset.add>`. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is no
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But this is a wrong name for anchor. We should do something with this.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree. I plan to fix it, but it requires changes (& a release) of Sphinx. This PR makes the reference link to the right place, and more importantly means that no future reference errors can be introduced into Once it is fixed, I plan to go back and update here & a few other places where we have used a different target to the intended one.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Now, I think that we should reorganize the set/frozenset documentation in the way similar to the sequence or bytes/bytearray documentation.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. #141857 implements this approach.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wrong reverence to |
||
| Since it is mutable, it has no hash value and cannot be used as | ||
| either a dictionary key or as an element of another set. | ||
| The :class:`frozenset` type is immutable and :term:`hashable` --- | ||
| its contents cannot be altered after it is created; | ||
| it can therefore be used as a dictionary key or as an element of another set. | ||
|
|
||
| Non-empty sets (not frozensets) can be created by placing a comma-separated list | ||
| of elements within braces, for example: ``{'jack', 'sjoerd'}``, in addition to the | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.