Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

PEP 797: Shared Object Proxies #4536

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

Open
ZeroIntensity wants to merge 8 commits into python:main
base: main
Choose a base branch
Loading
from ZeroIntensity:shared-object-proxies

Conversation

@ZeroIntensity
Copy link
Member

@ZeroIntensity ZeroIntensity commented Aug 8, 2025 •
edited
Loading

Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • Required sections included
    • Abstract (first section)
    • Copyright (last section; exact wording from template required)
  • Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • Suggested sections included (unless not applicable)
    • Motivation
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • Python-Version set to valid (pre-beta) future Python version, if relevant
  • Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

📚 Documentation preview 📚: https://pep-previews--4536.org.readthedocs.build/pep-0797/

@ZeroIntensity ZeroIntensity requested a review from a team as a code owner August 8, 2025 16:54
@brianschubert brianschubert added the new-pep A new draft PEP submitted for initial review label Aug 8, 2025
Abstract
========

This PEP introduces a new :func:`~concurrent.interpreters.share` function to
Copy link
Member

@AA-Turner AA-Turner Sep 19, 2025

Choose a reason for hiding this comment

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

Suggested change
This PEP introduces a new :func:`~concurrent.interpreters.share` function to
This PEP introduces a new :func:`!share` function to

Copy link
Member Author

@ZeroIntensity ZeroIntensity Nov 28, 2025

Choose a reason for hiding this comment

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

Wouldn't it be better to have a link?


from concurrent import interpreters

with open("spanish_inquisition.txt") as unshareable:
Copy link
Member

@AA-Turner AA-Turner Sep 19, 2025

Choose a reason for hiding this comment

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

always use an encoding!

Suggested change
with open("spanish_inquisition.txt") as unshareable:
with open('spanish_inquisition.txt', encoding='utf-8') as unshareable:

Copy link
Member Author

@ZeroIntensity ZeroIntensity Nov 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

We're in 3.15 now, UTF-8 is finally the default!

@ZeroIntensity ZeroIntensity changed the title (削除) PEP 797: Shared Object Proxies for Subinterpreters (削除ここまで) (追記) PEP 797: Shared Object Proxies (追記ここまで) Nov 27, 2025
Copy link
Member Author

Ok, I finally got back to this one.

@AA-Turner Following the discussion I had with Yury at the core sprint, I realized this works without immortality at all, which should resolve your concerns regarding the "context ID" thing and other implementation details. I rewrote the whole proposal with your comments in mind; could you take a second look?

Copy link
Member Author

Friendly bump 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AA-Turner AA-Turner Awaiting requested review from AA-Turner

Assignees

No one assigned

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /