All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5696] New: python3 installation is too large, patches from python2 needed
Date: Fri, 16 Nov 2012 10:01:59 +0000 (UTC)	[thread overview]
Message-ID: <bug-5696-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=5696

           Summary: python3 installation is too large, patches from
                    python2 needed
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: maxime.ripard at free-electrons.com
        ReportedBy: thomas.petazzoni at free-electrons.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Our Python 2 package has a bunch of patches (numbered 100 and above) that allow
to disable the build of a number of extensions that are not necessarily useful
in all situations. Those patches should be upgraded and added in our Python 3
package.

At the moment, the Python 3 installation takes 55 MB in /usr/lib/python3.3/,
which is way too much.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-11-16 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 10:01 bugzilla at busybox.net [this message]
2013-05-26 10:23 ` [Buildroot] [Bug 5696] python3 installation is too large, patches from python2 needed bugzilla at busybox.net
2013-06-29 19:46 ` bugzilla at busybox.net
2013-10-30 21:53 ` bugzilla at busybox.net

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=bug-5696-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.