From: Olof Johansson <olof.johansson@axis.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python] Python Flask recipes
Date: Fri, 19 Feb 2016 14:59:36 +0100 [thread overview]
Message-ID: <20160219135936.GA31212@axis.com> (raw)
In-Reply-To: <CAP9ODKpXkzdSki8exzpbge08Uns1M3rQcc2C1UTPGpuA-WUKOQ@mail.gmail.com>
On 16-02-19 11:32 -0200, Otavio Salvador wrote:
> Agreed but this is a specific framework which is not 'core' to python.
> Do you think we ought to merge those on meta-python or keep them split
> out?
Things that are really core to python are already in OE-Core,
built as part of the python recipe. Even if *I* don't use
something, I would expect a meta-python layer to include all
(reasonably common) parts of the python ecosystem, and doing web
applications is certainly one part of that.
--
olofjn
next prev parent reply other threads:[~2016-02-19 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:33 [meta-python] Python Flask recipes Fabio Berton
2016-02-19 3:46 ` Khem Raj
2016-02-19 4:58 ` Tim Orling
2016-02-19 13:32 ` Otavio Salvador
2016-02-19 13:59 ` Olof Johansson [this message]
2016-02-19 18:02 ` Khem Raj
2016-02-22 10:04 ` Anders Darander
2016-02-22 12:01 ` Otavio Salvador
2016-02-19 13:29 ` Otavio Salvador
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=20160219135936.GA31212@axis.com \
--to=olof.johansson@axis.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.