Skip to content

Fix pickeling#717

Open
Vizonex wants to merge 10 commits into
aio-libs:masterfrom
Vizonex:fix-pickeling
Open

Fix pickeling#717
Vizonex wants to merge 10 commits into
aio-libs:masterfrom
Vizonex:fix-pickeling

Conversation

@Vizonex
Copy link
Copy Markdown
Member

@Vizonex Vizonex commented Nov 6, 2025

What do these changes do?

I forgot I had made a fork for trying to fix pickling but I seemed to never bother to add it after the issuer told me there was no need but it seems it needs to come back. This PR adds in a new argument to freeze a frozenlist right away which is a tradeoff but it was the only way I could seem to get pickling to work correctly.

Are there changes in behavior for the user?

Related issue number

fixes #683

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modifications, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep the list in alphabetical order, the file is sorted by name.
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<category> for example (588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure category is one of the following:
      • .bugfix: Signifying a bug fix.
      • .feature: Signifying a new feature.
      • .breaking: Signifying a breaking change or removal of something public.
      • .doc: Signifying a documentation improvement.
      • .packaging: Signifying a packaging or tooling change that may be relevant to downstreams.
      • .contrib: Signifying an improvement to the contributor/development experience.
      • .misc: Anything that does not fit the above; usually, something not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

Comment thread frozenlist/__init__.py Fixed
@codecov
Copy link
Copy Markdown

codecov Bot commented May 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.74%. Comparing base (629fc8b) to head (60880e8).

Additional details and impacted files
@@             Coverage Diff             @@
##            master     #717      +/-   ##
===========================================
- Coverage   100.00%   99.74%   -0.26%     
===========================================
  Files            2        2              
  Lines          370      388      +18     
  Branches         9       10       +1     
===========================================
+ Hits           370      387      +17     
- Partials         0        1       +1     
Flag Coverage Δ
CI-GHA 99.74% <100.00%> (+0.01%) ⬆️
OS-Linux 99.74% <100.00%> (+0.01%) ⬆️
OS-Windows 99.74% <100.00%> (+0.01%) ⬆️
OS-macOS 99.74% <100.00%> (+0.01%) ⬆️
Py-3.10.11 99.74% <100.00%> (+0.01%) ⬆️
Py-3.10.20 99.74% <100.00%> (+0.01%) ⬆️
Py-3.11.15 99.74% <100.00%> (+0.01%) ⬆️
Py-3.11.9 99.74% <100.00%> (+0.01%) ⬆️
Py-3.12.10 99.74% <100.00%> (+0.01%) ⬆️
Py-3.12.13 99.74% <100.00%> (+0.01%) ⬆️
Py-3.13.13 99.74% <100.00%> (+0.01%) ⬆️
Py-3.13.13t 99.74% <100.00%> (+0.01%) ⬆️
Py-3.14.4 99.74% <100.00%> (+0.01%) ⬆️
Py-3.14.5 99.74% <100.00%> (+0.01%) ⬆️
Py-3.14.5t 99.74% <100.00%> (+0.01%) ⬆️
Py-pypy3.10.16-7.3.19 ?
VM-macos-latest 99.74% <100.00%> (+0.01%) ⬆️
VM-ubuntu-latest 99.74% <100.00%> (+0.01%) ⬆️
VM-windows-11-arm 99.74% <100.00%> (+0.01%) ⬆️
VM-windows-latest 99.74% <100.00%> (+0.01%) ⬆️
pytest 99.74% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bdraco
Copy link
Copy Markdown
Member

bdraco commented May 18, 2026

@Vizonex would you bring this back up to date?

@Vizonex
Copy link
Copy Markdown
Member Author

Vizonex commented May 19, 2026

@bdraco Sorry for the wait. I can.

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.

Release new version (with fixes for pickling)?

3 participants