WeakSet is not pickleable

Open

#74,876 opened on Jun 17, 2017 8 comments 0 reactions 0 assignees View on GitHub

@serhiy-storchaka is already working on this.

Since Jun 11, 2022.

#93732 by @serhiy-storchaka — open

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: python
Domain: backend

Research direction

Start by reading the linked PRs gh-93732 and gh-153818, then locate the affected CPython library entry point and determine the expected pickle behavior. Done means WeakSet can be pickled as requested and the behavior is covered by a focused regression test.

Written by the indexing model from the issue text.

Description

3.11 3.12 stdlib type-bug

BPO	30691
Nosy	@Yhg1s, @birkenfeld, @rhettinger, @pitrou, @serhiy-storchaka

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2017-06-17.18:54:10.235>
labels = ['library']
title = 'WeakSet is not pickleable'
updated_at = <Date 2017-06-18.06:09:54.301>
user = 'https://github.com/serhiy-storchaka'

bugs.python.org fields:

activity = <Date 2017-06-18.06:09:54.301>
actor = 'rhettinger'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-06-17.18:54:10.235>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 30691
keywords = []
message_count = 4.0
messages = ['296243', '296256', '296262', '296264']
nosy_count = 5.0
nosy_names = ['twouters', 'georg.brandl', 'rhettinger', 'pitrou', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue30691'
versions = []

Linked PRs

gh-93732
gh-153818

Dominant language: Python
Stars: 77.2k
Forks: 36k
Avg merge: 1d 9h
Merged PRs (30d): 558

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[feature][processing] Add profile selection options to qgis_process (Request in QGIS) Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

qgis/QGIS-Documentation#11275 · Opened Sep 21, 2026
fix(automation): do not restart an active subject delivery Open

bug priority:normal ready-for-dev

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

OpenHands/extensions#626 · 1 comment · Opened Sep 21, 2026
Change observation tooltip text Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

CSCfi/sd-search-api#39 · Opened Sep 21, 2026
Schema regression: derivation conversion_failure reverted Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

elong0527/yamaa#708 · Opened Sep 21, 2026
please add to porn list Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

StevenBlack/hosts#3255 · Opened Sep 21, 2026

More Python issues