All commit authors signed the Contributor License Agreement.

@encukou and @freakboy3742: Your comments would be welcome.

I like this idea

Hello,
As the sponsor, I apologize for not giving clear guidance. I expected Malcolm would share the draft with me privately first, so we'd get the details ironed out and the process straight. But I gave a note of what to do in case I wasn't available, which was, in hindsight, too brief.

The first round of discussions around an idea usually happens before a PEP number is assigned yet; the PEP is then written to discuss concrete (and specifically worded) proposal.
Here, the idea is sound and experts have been hammering out the details for years, so perhaps a PR -- and PEP number assignment -- is a good first step.
Regardless, the proposed PEP number should not be used before it's assigned. But since it has been used, I'd like to kindly ask that PEP editors do pick 738 :)

@encukou: Thanks, and sorry for the misunderstanding.

Hello, As the sponsor, I apologize for not giving clear guidance.

Apologies on my part, as well - @mhsmith was following what I did with PEP 730, which didn't go through this "pre-release" process.

@mhsmith, it's OK to leave any suggestions to a future revision, especially ones asking for significant rewording, expanding, or adding new sections.
That doesn't mean those comments aren't welcome, of course! Definitely put them on your TODO list. But you can focus this PR on getting an initial version of the PEP published.

@freakboy3742 Yeah, the sprint allowed a higher-throughput process :)
No harm done, I hope.

@encukou: Thanks, I'll do that.

Main changes:

• Added more justification for the choice of target Android versions and architectures.
• Gathered coverage of development tools into a new section, and added information about NDK versions.
• Added a deliverable for documentation of how to use the embeddable package.

@freakboy3742, @willingc, @encukou: I think this addresses all of your comments, so please resolve your conversations or comment more as appropriate. I know we're getting into the holiday season now, so take as long as you like.

There are some other open discussions on the Discourse thread, but I'll leave those until the next draft.

@willingc, @encukou: Happy new year! Please resolve your open conversations when you get a chance, as I think this PR is ready to merge. I'll then look into the other points that were raised on the Discourse thread, and create a separate PR with a second draft.

@willingc, @encukou: Happy new year! Please resolve your open conversations when you get a chance, as I think this PR is ready to merge. I'll then look into the other points that were raised on the Discourse thread, and create a separate PR with a second draft.

@mhsmith Done. Thanks so much for getting this PEP done 🎉

Thanks for the ping!

Congratulations, it's a PEP!