From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python3: Downgrade to 3.6.6
Date: Tue, 25 Sep 2018 21:56:43 +0200 [thread overview]
Message-ID: <20180925215643.6d5c08b6@windsurf> (raw)
In-Reply-To: <CALFsTFWZYhJtMqb+ksXtJ=1FPOOm-_ynP-vD_i71ttjBEdC=oA@mail.gmail.com>
Hello,
On Tue, 25 Sep 2018 22:28:11 +0300, Asaf Kahlon wrote:
> I disagree with downgrading... Are we really sure the downgrade is needed?
> Some patches I sent for python 3.7 packages have already applied (gunicorn,
> paramiko etc), I sent a series of patches for pysnmp (
> http://patchwork.ozlabs.org/project/buildroot/list/?series=67049), and I
> saw you sent a first patch for django (
> http://patchwork.ozlabs.org/patch/973261/). So I think we've made a nice
> progress until now.
> What would be left after that? I think the main packages are crossbar and
> twisted. Both have a newer version to upgrade and both seem to have active
> repository on github. Maybe it won't be so hard to fix those packages. I
> think you should give it a shot before downgrading, but i'm willing to hear
> other opinions too.
For now, I also dislike the idea of downgrading, because it doesn't
seem that the number of affected packages is that important.
Asaf, do you think you could help in that effort, perhaps by looking at
crossbar and twisted ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-25 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 18:03 [Buildroot] [PATCH 1/1] python3: Downgrade to 3.6.6 Adam Duskett
2018-09-25 19:28 ` Asaf Kahlon
2018-09-25 19:56 ` Thomas Petazzoni [this message]
2018-09-25 20:12 ` Asaf Kahlon
2018-09-25 22:41 ` Adam Duskett
2018-09-26 2:53 ` Ricardo Martincoski
2018-09-26 2:54 ` Ricardo Martincoski
2018-09-26 7:29 ` 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=20180925215643.6d5c08b6@windsurf \
--to=thomas.petazzoni@bootlin.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