From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 08/08] package/python-channels-redis: new package
Date: Mon, 30 Sep 2019 22:09:40 +0200 [thread overview]
Message-ID: <20190930220940.386dbcb0@windsurf.home> (raw)
In-Reply-To: <20190804011631.86261-9-aduskett@gmail.com>
Hello,
+Yegor here as well, as I have a Python packaging question.
On Sat, 3 Aug 2019 21:16:31 -0400
aduskett at gmail.com wrote:
> diff --git a/package/python-channels-redis/Config.in b/package/python-channels-redis/Config.in
> new file mode 100644
> index 0000000000..75b90837e5
> --- /dev/null
> +++ b/package/python-channels-redis/Config.in
> @@ -0,0 +1,17 @@
> +config BR2_PACKAGE_PYTHON_CHANNELS_REDIS
> + bool "python-channels-redis"
> + depends on BR2_TOOLCHAIN_HAS_ATOMIC # redis
> + select BR2_PACKAGE_PYTHON_AIOREDIS # runtime
> + select BR2_PACKAGE_PYTHON_MSGPACK # runtime
> + select BR2_PACKAGE_PYTHON_ASGIREF # runtime
> + select BR2_PACKAGE_PYTHON_CHANNELS # runtime
> + select BR2_PACKAGE_REDIS
Here as well, we don't need this BR2_PACKAGE_REDIS dependency. The
other dependencies should be ordered alphabetically, and the
BR2_PACKAGE_PYTHON3 dependency was missing. I fixed all that and
applied.
Now, the question for which Yegor's input would also be useful. The
setup.py for this package goes like this:
crypto_requires = ["cryptography>=1.3.0"]
test_requires = crypto_requires + [
"pytest~=3.6.0",
"pytest-asyncio~=0.8",
"async_generator~=1.8",
"async-timeout~=2.0",
]
setup(
[...]
install_requires=[
"aioredis~=1.0",
"msgpack~=0.6.0",
"asgiref~=3.0",
"channels~=2.2",
],
extras_require={"cryptography": crypto_requires, "tests": test_requires},
)
The question is how do these "extras_require" work ? While we don't
care much about the tests, the cryptography stuff maybe be useful. How
does it work ? Does it say "I'm able to use python-cryptography>1.3.0
if it's available" ? Is there anything that needs to be done to
'enable' this dependency ? Should we have a sub-option for this ? Or
make it an automatic dependency, which means basically do nothing since
these are pure runtime dependencies anyway ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-09-30 20:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 1:16 [Buildroot] [PATCH 00/13] Support for Django channels aduskett at gmail.com
2019-08-04 1:16 ` [Buildroot] [PATCH 01/08] package/python-django-enumfields: new package aduskett at gmail.com
2019-09-27 21:41 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 02/08] package/python-sqlparse: " aduskett at gmail.com
2019-09-27 21:49 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 03/08] package/python-hiredis: " aduskett at gmail.com
2019-08-04 5:53 ` Yegor Yefremov
2019-08-04 10:18 ` Peter Korsgaard
2019-08-04 1:16 ` [Buildroot] [PATCH 04/08] package/python-daphne: " aduskett at gmail.com
2019-08-04 5:58 ` Yegor Yefremov
2019-09-30 19:33 ` Thomas Petazzoni
2019-09-30 19:58 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 05/08] package/python-asgiref: " aduskett at gmail.com
2019-09-27 21:55 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 06/08] package/python-aioredis: " aduskett at gmail.com
2019-09-30 19:43 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 07/08] package/python-channels: " aduskett at gmail.com
2019-09-30 19:58 ` Thomas Petazzoni
2019-08-04 1:16 ` [Buildroot] [PATCH 08/08] package/python-channels-redis: " aduskett at gmail.com
2019-09-30 20:09 ` Thomas Petazzoni [this message]
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=20190930220940.386dbcb0@windsurf.home \
--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