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

Add A Howto Page About Using Multiple Interpreters #121817

Closed
ericsnowcurrently opened this issue Jul 15, 2024 · 5 comments
Closed

Add A Howto Page About Using Multiple Interpreters #121817

ericsnowcurrently opened this issue Jul 15, 2024 · 5 comments
Assignees
Labels
3.13 bugs and security fixes 3.14 new features, bugs and security fixes docs Documentation in the Doc dir topic-subinterpreters

Comments

@ericsnowcurrently
Copy link
Member

While subinterpreters are not a new feature, there isn't much information about how to use them. Part of this is because there is no stdlib module that exposes them to users (see PEP 734). Regardless, it would be helpful to have a new Howto document that gives some instruction.

The page would include the following:

  • how to create and use a subinterpreter from Python code (via my PEP 734 implementation on PyPI)
  • how to communicate between interpreters
  • a series of examples of how to use multiple interpreters for different concurrency/parallelism needs
  • some minimal comparisons with multiprocessing, threads, and async
@ericsnowcurrently ericsnowcurrently added docs Documentation in the Doc dir topic-subinterpreters 3.13 bugs and security fixes 3.14 new features, bugs and security fixes labels Jul 15, 2024
@ericsnowcurrently ericsnowcurrently self-assigned this Jul 15, 2024
@benjamin-kirkbride
Copy link

via my PEP 734 implementation on PyPI

Could you provide a link? Sounds interesting :)

@erlend-aasland
Copy link
Contributor

via my PEP 734 implementation on PyPI

Could you provide a link? Sounds interesting :)

https://pypi.org/project/interpreters-pep-734/

@ericsnowcurrently
Copy link
Member Author

FYI, I expect that I'll be moving that package to a different org and potentially renaming it (to "interpreters").

The @python/steering-council asked that I put up a PyPI package to get feedback before PEP 734 may be accepted. However, we still haven't settled what approach to take on PyPI. The most likely solution is a new PyPI org for semi-official packages (or perhaps just for packages that are under consideration for stdlib inclusion). I would like to resolve that before landing this new Howto page.

@hugovk
Copy link
Member

hugovk commented Jul 17, 2024

By the way, we requested the "python" and "cpython" orgs in December, but there's currently a big backlog in dealing with org requests. The good news is the PSF has just hired a PyPI Support Specialist to work on things like this.

@ericsnowcurrently
Copy link
Member Author

I'll probably table this in favor of gh-123152.

@ericsnowcurrently ericsnowcurrently closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.13 bugs and security fixes 3.14 new features, bugs and security fixes docs Documentation in the Doc dir topic-subinterpreters
Projects
Status: Done
Development

No branches or pull requests

4 participants