From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] python3: Bump version to 3.6.0
Date: Wed, 8 Mar 2017 00:05:46 +0100 [thread overview]
Message-ID: <20170308000546.6f63414e@free-electrons.com> (raw)
In-Reply-To: <20170306224852.30968-2-andrew.smirnov@gmail.com>
Hello,
On Mon, 6 Mar 2017 14:48:52 -0800, Andrey Smirnov wrote:
> Update all appropriate version numbers as well as SHAs and MD5s as well
> as repbasing BR's patches on top of 3.6.0 codebase (new github repo
> tree, v3.6.0 tag was used). Note that patches:
>
> [PATCH] Change the install location of _sysconfigdata.py
> [PATCH] distutils/sysconfig: use sysconfigdata
>
> were dropped from the patchset since 3.6.0 codebase doesn't seem like it
> has the problem that aforementioned patches were solving.
It would be nice to have more details on how this sysconfigdata thing
changed. I don't remember the details (it's been a long time), but I
remember that thing being particularly being, so I would like to be
extra cautious when getting rid of patches in the python(3) packages.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-07 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 22:48 [Buildroot] [PATCH 1/2] scripts/pycompile: Accomodate latest Python 3 codebase Andrey Smirnov
2017-03-06 22:48 ` [Buildroot] [PATCH 2/2] python3: Bump version to 3.6.0 Andrey Smirnov
2017-03-07 23:05 ` Thomas Petazzoni [this message]
2017-03-10 5:47 ` Andrey Smirnov
2017-03-07 23:04 ` [Buildroot] [PATCH 1/2] scripts/pycompile: Accomodate latest Python 3 codebase Thomas Petazzoni
2017-03-08 8:39 ` Yegor Yefremov
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=20170308000546.6f63414e@free-electrons.com \
--to=thomas.petazzoni@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