* Re: [meta-python] Python Flask recipes
2016-02-19 13:32 ` Otavio Salvador
@ 2016-02-19 13:59 ` Olof Johansson
2016-02-19 18:02 ` Khem Raj
2016-02-22 10:04 ` Anders Darander
2 siblings, 0 replies; 9+ messages in thread
From: Olof Johansson @ 2016-02-19 13:59 UTC (permalink / raw)
To: openembedded-devel
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-python] Python Flask recipes
2016-02-19 13:32 ` Otavio Salvador
2016-02-19 13:59 ` Olof Johansson
@ 2016-02-19 18:02 ` Khem Raj
2016-02-22 10:04 ` Anders Darander
2 siblings, 0 replies; 9+ messages in thread
From: Khem Raj @ 2016-02-19 18:02 UTC (permalink / raw)
To: openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
> On Feb 19, 2016, at 5:32 AM, Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
>
> On Fri, Feb 19, 2016 at 1:46 AM, Khem Raj <raj.khem@gmail.com> wrote:
>>> On Feb 18, 2016, at 10:33 AM, Fabio Berton <fabio.berton@ossystems.com.br> wrote:
>>> I noticed that a few days ago were added some python-flask recipes.
>>>
>>> I've been maintaining a layer with python-flask recipes, hosted here
>>> http://code.ossystems.com.br/gitweb?p=meta-python-flask.git;a=summary
>>>
>>> There are recipes in meta-python-flask that were added to meta-python
>>> and I want to simplify maintenance and avoid duplicate recipes.
>>>
>>> So, do I send recipes from meta-python-flask to meta-python or we move all
>>> python-flask recipes from meta-python to meta-python-flask, using a layer
>>> only for Flask web framework?
>>
>> Here is a hierarchy one can envision
>>
>> 1. Core python runtime support - Oe-core
>> 2. python extended modules and infrastructure - meta-python
>>
>> now if you think this framework is quite commonly used and is kind of core
>> to python world, its fine to have it in meta-python, if you think its
>> too specific then move the common packages to meta-python
>> and maintain it as a separate layer
>
> 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?
Just review it and common pieces can move to meta-python, so you can
remove unnecessary recipe copies in multiple layers in future. I don’t
have a strong opinion on the framework itself. It can probably stay in
its own layer if its not so commonly used.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-python] Python Flask recipes
2016-02-19 13:32 ` Otavio Salvador
2016-02-19 13:59 ` Olof Johansson
2016-02-19 18:02 ` Khem Raj
@ 2016-02-22 10:04 ` Anders Darander
2016-02-22 12:01 ` Otavio Salvador
2 siblings, 1 reply; 9+ messages in thread
From: Anders Darander @ 2016-02-22 10:04 UTC (permalink / raw)
To: openembedded-devel
* Otavio Salvador <otavio.salvador@ossystems.com.br> [160219 14:32]:
> On Fri, Feb 19, 2016 at 1:46 AM, Khem Raj <raj.khem@gmail.com> wrote:
> >> On Feb 18, 2016, at 10:33 AM, Fabio Berton <fabio.berton@ossystems.com.br> wrote:
> >> I noticed that a few days ago were added some python-flask recipes.
> >> I've been maintaining a layer with python-flask recipes, hosted here
> >> http://code.ossystems.com.br/gitweb?p=meta-python-flask.git;a=summary
> >> There are recipes in meta-python-flask that were added to meta-python
> >> and I want to simplify maintenance and avoid duplicate recipes.
> >> So, do I send recipes from meta-python-flask to meta-python or we move all
> >> python-flask recipes from meta-python to meta-python-flask, using a layer
> >> only for Flask web framework?
> > Here is a hierarchy one can envision
> > 1. Core python runtime support - Oe-core
> > 2. python extended modules and infrastructure - meta-python
> > now if you think this framework is quite commonly used and is kind of core
> > to python world, its fine to have it in meta-python, if you think its
> > too specific then move the common packages to meta-python
> > and maintain it as a separate layer
> 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?
I'd lean towards merging them in meta-python.
Currently (according to the layerindex) we have python-flask in:
* meta-virtualization
* meta-uav
* meta-python
and if I understood your other email correct, there's also your
meta-python-flask layer.
I'd think that this makes flask used enough to warrant having it
directly in meta-python.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-python] Python Flask recipes
2016-02-22 10:04 ` Anders Darander
@ 2016-02-22 12:01 ` Otavio Salvador
0 siblings, 0 replies; 9+ messages in thread
From: Otavio Salvador @ 2016-02-22 12:01 UTC (permalink / raw)
To: OpenEmbedded Devel List, Fabio Berton
On Mon, Feb 22, 2016 at 7:04 AM, Anders Darander <anders@chargestorm.se>
wrote:
> * Otavio Salvador <otavio.salvador@ossystems.com.br> [160219 14:32]:
>
> > On Fri, Feb 19, 2016 at 1:46 AM, Khem Raj <raj.khem@gmail.com> wrote:
> > >> On Feb 18, 2016, at 10:33 AM, Fabio Berton <
> fabio.berton@ossystems.com.br> wrote:
> > >> I noticed that a few days ago were added some python-flask recipes.
>
> > >> I've been maintaining a layer with python-flask recipes, hosted here
> > >> http://code.ossystems.com.br/gitweb?p=meta-python-flask.git;a=summary
>
> > >> There are recipes in meta-python-flask that were added to meta-python
> > >> and I want to simplify maintenance and avoid duplicate recipes.
>
> > >> So, do I send recipes from meta-python-flask to meta-python or we
> move all
> > >> python-flask recipes from meta-python to meta-python-flask, using a
> layer
> > >> only for Flask web framework?
>
> > > Here is a hierarchy one can envision
>
> > > 1. Core python runtime support - Oe-core
> > > 2. python extended modules and infrastructure - meta-python
>
> > > now if you think this framework is quite commonly used and is kind of
> core
> > > to python world, its fine to have it in meta-python, if you think its
> > > too specific then move the common packages to meta-python
> > > and maintain it as a separate layer
>
> > 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?
>
> I'd lean towards merging them in meta-python.
>
> Currently (according to the layerindex) we have python-flask in:
> * meta-virtualization
> * meta-uav
> * meta-python
>
> and if I understood your other email correct, there's also your
> meta-python-flask layer.
>
> I'd think that this makes flask used enough to warrant having it
> directly in meta-python.
>
Ok; this is indeed a good justification.
Fabio, lets send the patches to include the recipes on meta-python and also
for the other layers to remove the respective recipes from them.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 9+ messages in thread