Skip to content
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

bpo-40521: Empty frozenset is no longer a singleton #21085

Merged
merged 3 commits into from
Jun 23, 2020

Conversation

rhettinger
Copy link
Contributor

@rhettinger rhettinger commented Jun 23, 2020

Making the empty frozenset a singleton wasn't worth it. Unlike empty strings and empty tuples, these are not common and don't warrant a special case. Taking it out makes the code simpler.

https://bugs.python.org/issue40521

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@vstinner
Copy link
Member

I merged the PR since I'm working on other changes which are in conflict with this PR, like PR #21086.

fasih pushed a commit to fasih/cpython that referenced this pull request Jun 29, 2020
* Revert "bpo-40521: Make the empty frozenset per interpreter (pythonGH-21068)"

This reverts commit 261cfed.

* bpo-40521: Empty frozensets are no longer singletons

* Complete the removal of the frozenset singleton
arun-mani-j pushed a commit to arun-mani-j/cpython that referenced this pull request Jul 21, 2020
* Revert "bpo-40521: Make the empty frozenset per interpreter (pythonGH-21068)"

This reverts commit 261cfed.

* bpo-40521: Empty frozensets are no longer singletons

* Complete the removal of the frozenset singleton
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants