This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pmpp
Recipients ned.deily, pmpp, vstinner, yan12125
Date 2018-01-28.15:54:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1517154888.39.0.467229070634.issue32654@psf.upfronthosting.co.za>
In-reply-to
Content
@yan12125
Hi, I ran some tests too and here are my findings:
 https://github.com/pmp-p/droid-pydk/tree/master/sources.32/build_logs

* I used some dirty patchset to cover more tests https://github.com/pmp-p/droid-pydk/tree/master/sources.32/cpython-bpo-30386.patchset i would be glad if you could have a look at them, as i am not a C/C++ programmer (i'm "pmpp" on IRC where we met last time).

* Maybe SIG* stuff is fixed only for unified headers API>=21 regardless of NDK that would need checking. 

* python build quite fine will all NDK ( sorry to say but especially the non vendor one can support cpython for prehistoric api and  version 3.5/3.6 *without patches* under certain condition of use )

my thoughts :

* Only third parties libs that have trouble with NDK versions, like openssl but libssl and libcrypto are provided by OS.

* Third parties are not required to embed libpython. Xavier de Gaye's script use shared linking. you should be able to provide whatever version of those you need that's not a cpython's build script job to deal with that, imho it was just for demontrasting that android build can be easy. I personnally would not build my third parties that way.

*  non official cpython build runs very well after android 5.0 there's almost nothing to do left, and micropython is able to run everywhere cpython can't (yet) so nothing is impossible.

* old api are frozen, there won't be suddenly a lot to support, when devices using them will vanish from asian stores it will mark the end of them and their need of support : imho there's no "end of life/support" concept for android os.

* I'd like a possible api19 "best effort", because android kitkat vendor statistics are wrong they don't take into account the *huge* amount of gservice-less devices.

unclear if unrelated to this:

* platform=='android' shoud be set, regardless of any API version : Android platform exists and is already running some pythons, it is a fact.

Thanks Victor for trying to clean my patchset : i did not realize my embed use of libpython could help official cpython too. Anyway I would be glad to help this way or another.
History
Date User Action Args
2018-01-28 15:54:48pmppsetrecipients: + pmpp, vstinner, ned.deily, yan12125
2018-01-28 15:54:48pmppsetmessageid: <1517154888.39.0.467229070634.issue32654@psf.upfronthosting.co.za>
2018-01-28 15:54:48pmpplinkissue32654 messages
2018-01-28 15:54:48pmppcreate