From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/python-iniparse: bump to version 0.5
Date: Wed, 5 Feb 2020 16:42:50 +0100 [thread overview]
Message-ID: <20200205164250.338d5c6e@windsurf> (raw)
In-Reply-To: <20200205141149.20749-2-titouan.christophe@railnova.eu>
On Wed, 5 Feb 2020 15:11:47 +0100
Titouan Christophe <titouan.christophe@railnova.eu> wrote:
> Also, iniparse now requires six.
> This has been detected thanks to the runtime tests.
It would have been good to mention in the commit log that it now supports Python 3.
> config BR2_PACKAGE_PYTHON_INIPARSE
> bool "python-iniparse"
> - depends on BR2_PACKAGE_PYTHON
> + depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
This is not needed when both are supported, since Python modules
Config.in files are only included when python || python3, from
package/Config.in.
Applied with the above issues fixed. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-05 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:11 [Buildroot] [PATCH 0/3] package/crudini: make it Python3 compatible Titouan Christophe
2020-02-05 14:11 ` [Buildroot] [PATCH 1/3] package/python-iniparse: bump to version 0.5 Titouan Christophe
2020-02-05 15:42 ` Thomas Petazzoni [this message]
2020-02-05 14:11 ` [Buildroot] [PATCH 2/3] package/crudini: bump to version 0.9.3 Titouan Christophe
2020-02-05 15:43 ` Thomas Petazzoni
2020-02-05 14:11 ` [Buildroot] [PATCH 3/3] support/testing: add runtime test for Crudini (py2 and py3) Titouan Christophe
2020-02-05 15:44 ` Thomas Petazzoni
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=20200205164250.338d5c6e@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 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.