Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] python3: Port python2 patches to reduce the interpreter size
Date: Wed, 23 Jan 2013 09:27:34 +0100	[thread overview]
Message-ID: <50FF9EF6.2020603@free-electrons.com> (raw)
In-Reply-To: <50FAD25E.4010608@mind.be>

Hi Arnout,

On 19/01/2013 18:05, Arnout Vandecappelle wrote:
> On 18/01/13 15:06, Maxime Ripard wrote:
>> Some of the python2 patches were left behind when doing the python3
>> package. This was because the python build system can now autodetect
>> what packages can be built in the system.
>>
>> However, some of these patches are actually useful to reduce drastically
>> the size of the interpreter.
>>
>> This patch ports the relevant patches to the python3 package, and adds a
>> new patch to remove the idle3 IDE as well from the interpreter.
>>
>> Fixes #5696
>>
>> Signed-off-by: Maxime Ripard<maxime.ripard@free-electrons.com>
>> ---
>>   package/python3/Config.in                          |   11 ++
>>   .../python3-3.3-012-disable-extensions.patch       |   98
>> +++++++++++++++++
> 
>  You should remove the -3.3- from the patch names. I know they're there
> in the old package, but this is a good opportunity to get rid of that
> legacy.

Right. Will do.

>  BTW, do these patches have a chance of getting upstreamed?

I don't think so, since most of them breaks (on purpose) the python
standard modules...

Maxime
-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-23  8:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 14:06 [Buildroot] [PATCH 1/3] python3: Point /usr/bin/python to python3 if python is not selected Maxime Ripard
2013-01-18 14:06 ` [Buildroot] [PATCH 2/3] python3: Port python2 patches to reduce the interpreter size Maxime Ripard
2013-01-19 14:53   ` Samuel Martin
2013-01-19 16:36     ` Samuel Martin
2013-01-23  8:26       ` Maxime Ripard
2013-01-23  8:25     ` Maxime Ripard
2013-01-23  8:39       ` Samuel Martin
2013-01-19 17:05   ` Arnout Vandecappelle
2013-01-23  8:27     ` Maxime Ripard [this message]
2013-01-18 14:06 ` [Buildroot] [PATCH 3/3] python3: Handle properly the pyc and py files on the target Maxime Ripard
2013-01-19 14:52   ` Samuel Martin
2013-01-20 20:38   ` Peter Korsgaard
2013-01-19 14:52 ` [Buildroot] [PATCH 1/3] python3: Point /usr/bin/python to python3 if python is not selected Samuel Martin
2013-01-20 20:34 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50FF9EF6.2020603@free-electrons.com \
    --to=maxime.ripard@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox