Skip to content

Conversation

@progval
Copy link

@progval progval commented Oct 20, 2024

In multiprocessing and concurrent.futures's documentations, as well as the release notes for Python 3.14.

This moves the paragraph in 3.14's release notes from the deprecations section to 'Porting to Python 3.14' because it is a breaking change, which follows a deprecation in Python 3.12.

This explicitly mentions PicklingError in this section, so it is easy to find for somehow who gets the error and searches its name through the page.


📚 Documentation preview 📚: https://cpython-previews--125750.org.readthedocs.build/

… through the fork method

In multiprocessing and concurrent.futures's documentations, as well as
the release notes for Python 3.14.

This moves the paragraph in 3.14's release notes from the deprecations
section to 'Porting to Python 3.14' because it is a breaking change,
which follows a deprecation in Python 3.12.

This explicitly mentions `PicklingError` in this section, so it is easy
to find for somehow who gets the error and searches its name through
the page.
@progval progval requested a review from gpshead as a code owner October 20, 2024 06:25
@ghost
Copy link

ghost commented Oct 20, 2024

The following commit authors need to sign the Contributor License Agreement:

Click the button to sign:
CLA not signed

@progval
Copy link
Author

progval commented Oct 20, 2024

Is it possible to skip the CLA for such a small change?

@rruuaanng
Copy link
Contributor

You must sign the CLA, which gives us permission to distribute your work.

Copy link
Member

@gpshead gpshead left a comment

Choose a reason for hiding this comment

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

Thanks!

@gpshead gpshead added the needs backport to 3.13 bugs and security fixes label Oct 20, 2024
Co-authored-by: Jelle Zijlstra <[email protected]>
@JelleZijlstra
Copy link
Member

I am afraid you will have to sign the CLA.

@progval
Copy link
Author

progval commented Oct 23, 2024

You must sign the CLA, which gives us permission to distribute your work.

I already did by submitting this PR after accepting Github's terms of service:

Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms.

Nonetheless, I'm fine with the CLA on principle, but I'm not willing to give out the personal info the cla-bot or the form are asking for.

@willingc
Copy link
Contributor

I'm going to go ahead and close this PR if there is no signed CLA. If someone wishes to work with @progval to take over this work, we can reopen the PR. Thanks @progval for your effort.

@willingc willingc closed this Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting merge docs Documentation in the Doc dir needs backport to 3.13 bugs and security fixes skip news

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants