Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] python-falcon: new package
Date: Thu, 30 Aug 2018 09:31:28 +0200	[thread overview]
Message-ID: <20180830093128.5d1f5837@windsurf> (raw)
In-Reply-To: <CAMWSM7gW28RJsfcBOFO4dGE4sEVncv4GRvxa3n_X8YQfXa_wDw@mail.gmail.com>

Hello,

On Wed, 29 Aug 2018 14:58:34 -0700, Joseph Kogut wrote:

> Cython allows Python modules to be written using a mix of Python and C
> or C++ syntax with optional static typing. During setup, Cython
> modules are transpiled to C or C++ and compiled normally as Python
> extensions. Most projects that use Cython, including Falcon, have
> implementations in vanilla Python, as well as Cython.
> 
> Based on my experience porting Kivy, having Cython available on the
> host should be enough to compile the extensions.

Thanks for the explanation/introduction about Cython!

> As I noted in my message after this one, I can't think of a reason to
> not *always* depend on host-cython here. Compiling the extensions is
> essentially an optimization step.
> 
> The only reason I can think of to not compile the extensions is if
> performance isn't a concern, and you don't have the requisite build
> environment during setup.

A principle in Buildroot is to avoid adding mandatory dependencies if
they are optional. So if people want the extra optimizations provided
by Cython, they should enable Cython, and python-falcon should
optionally depend on it.

Will you send a patch doing this ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-30  7:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 10:16 [Buildroot] [PATCH 1/2] python-mimeparse: new package Grzegorz Blach
2018-08-28 10:16 ` [Buildroot] [PATCH 2/2] python-falcon: " Grzegorz Blach
2018-08-28 10:18   ` Yegor Yefremov
2018-08-28 16:34   ` Joseph Kogut
2018-08-29 19:47     ` Thomas Petazzoni
2018-08-29 20:25       ` Grzegorz Blach
2018-08-29 20:37         ` Thomas Petazzoni
2018-08-29 21:58       ` Joseph Kogut
2018-08-30  7:31         ` Thomas Petazzoni [this message]
2018-08-30 10:20           ` Grzegorz Blach
2018-08-29 19:44   ` Thomas Petazzoni
2018-08-29 19:45     ` Yegor Yefremov
2018-08-28 10:18 ` [Buildroot] [PATCH 1/2] python-mimeparse: " Yegor Yefremov
2018-08-29 19:17 ` Thomas Petazzoni
2018-08-29 19:46 ` Thomas Petazzoni
2018-08-29 20:03   ` 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=20180830093128.5d1f5837@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