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 xdegaye
Recipients Alex.Willmer, doko, edmorley, martin.panter, thomas-petazzoni, vstinner, xdegaye, yan12125
Date 2017-10-21.20:11:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Ah, the discussion restarted on the other issue:

Issue 20210 has ended up as a change in the build system eventually and not the installation process, only a tiny step towards the configuration of a smaller Python distribution :(

After browsing again the last discussion on "[Python-ideas] size of the installation of Python on mobile devices" [1], I find all the arguments in favor of such changes still relevant. I would also add the following new arguments:

* One frequent argument used against those changes is that "[packagers for mobile and embedded devices] will have to patch the code base anyway to get things working in such an environment". But this is not true, see issue 30386 (Add a build infrastructure for Android) that proposes an addition to Python that does not modify a SINGLE LINE in the existing source code. So it is not true (or at least not anymore true) that packagers for mobile and embedded devices need to patch the code base anyway.

* When Python is installed by the termux [2] Android application on an Android device, the size of the installed standard library is 34M. The termux installation script does not install the following files [3]:

    bin/python${_MAJOR_VERSION}m bin/idle*

But it fails to not install also:

This is not consistent and should be fixed by a proper (endorsed by Python) installation process.

Date User Action Args
2017-10-21 20:11:36xdegayesetrecipients: + xdegaye, doko, vstinner, martin.panter, thomas-petazzoni, edmorley, Alex.Willmer, yan12125
2017-10-21 20:11:36xdegayesetmessageid: <>
2017-10-21 20:11:36xdegayelinkissue27640 messages
2017-10-21 20:11:36xdegayecreate