Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python enhancements
Date: Thu, 17 Jan 2008 17:37:44 +1100	[thread overview]
Message-ID: <20080117063744.GA1661@cloud.net.au> (raw)

Here are some enhancements for the python package.

1. Currently it strips .pyc (compiled python modules) from the build.
Instead, I added the option to strip the .py files instead, or keep
both. It's much quicker to load from the .pyc files and you often don't
even need the .py sources.

2. Currently a bunch of modules are disabled because they need extra
modules (openssl, readline, ncurses etc). I added configuration options
to enable them.

3. I also added an option to disable some of the larger compiled modules
(> 100k each) which are not used much.



Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br-python.patch
Type: text/x-diff
Size: 5552 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080117/5e6a6c00/attachment.bin 

                 reply	other threads:[~2008-01-17  6:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080117063744.GA1661@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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