Who to invite/notify about this project? #1
And relevant projects should send a PR to add themselves and their point of contact in the README. |
Replies: 5 comments 6 replies
|
BeeWare. PyInstaller. Bazel rules_python. Pants build. All groups I've interacted with as part of building PBS + PyOxidizer. I'm probably missing some. |
|
I can reach out to Russell for BeeWare. Do you (or anyone else) have contacts for the other projects? |
|
I reached out to @rickeylev and @aignas from rules_python on Bazel slack. |
|
In a similar vein: Nuitka |
|
The CPython release team, in particular, those involved in building current binary releases |
|
You're about to find out thanks to the post I'm writing on DPO. 😉 |
|
Probably should include Seth Larson to help ensure that current and emerging software supply chain security requirements are addressed in whatever is produced |
|
I opened #17 as a reminder for folks representing a project to please update the README so I know who may need to be explicitly looped in on anything. |
|
Hi — I'm Jasen, the author of pyr, a Python project manager that bootstraps its own CPython runtime. We're currently using Astral's python-build-standalone for that, and given recent events I've been watching this project closely. Happy to switch to official python.org builds when they're ready. Just wanted to plant a flag and say we're here. |
I opened #17 as a reminder for folks representing a project to please update the README so I know who may need to be explicitly looped in on anything.