-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
PEP 730: More revisions and clarifications #3529
Conversation
Co-authored-by: Malcolm Smith <smith@chaquo.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have access to resolve discussions in this repository, but all my comments have now been addressed.
@hugovk @ned-deily Checking in on this - is there anything outstanding preventing a merge, or did this just fall through the review cracks? |
The latter, sorry! |
@ned-deily: I don't think we've been properly introduced, but I'm the Android expert on the BeeWare team, and I'm planning to create an Android equivalent of this PEP. Is it OK if I list you as the sponsor? |
In case Ned wants to stay on the Apple side of things, and we don't find a core dev familiar with Android/Java native integration, I'd be happy to sponsor that PEP. |
Hello, @mhsmith! Consider yourself properly introduced. I'm not just at home in the Apple side of things but I am a stranger in the world of Android. So, having no special knowledge or any experience with Android, I would prefer if another core developer takes on the role of PEP sponsor for that. Thanks, @encukou! |
Thanks very much; I should have a first draft ready next week. There won't actually be much Java involved – as far as Python is concerned, Android is mostly just a variant of Linux. |
So soon! That's great! |
The Android PEP is now up for review at #3586. |
A second pass of revisions and clarifications on PEP 730, adding Tier 3 iOS support.
Adds an explicit mention of iPadOS
Proposes linking binary modules with libPython to avoid a deprecated compiler option
Proposes dropping static libPython.a builds as a supported output format
Clarifies the compilation process and the relationship between the configure/make/make install build and the useable artefacts.
Change is either:
PR title prefixed with PEP number (e.g.
PEP 123: Summary of changes
)📚 Documentation preview 📚: https://pep-previews--3529.org.readthedocs.build/