On Fri, Mar 4, 2022 at 3:14 PM Khem Raj wrote:
>
> On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
> >
> > If it's about meta-python why can't be placed there? I don't follow the
> > argument that some edge case stuff outside of core requires the project to
> > have additional (as of now
On 4 Mar 2022 21:14, Khem Raj wrote:On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
>
> If it's about meta-python why can't be placed there? I don't follow the argument that some edge case stuff outside of core requires the project to have additional (as of now not time limited) maintena
On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
>
> If it's about meta-python why can't be placed there? I don't follow the
> argument that some edge case stuff outside of core requires the project to
> have additional (as of now not time limited) maintenance effort - if there
> would be
If it's about meta-python why can't be placed there? I don't follow the argument that some edge case stuff outside of core requires the project to have additional (as of now not time limited) maintenance effort - if there would be a clear plan to remove that before kirkstone release I might agree,
On Fri, Mar 4, 2022 at 10:01 AM Otavio Salvador
wrote:
>
>
>
> Em sex., 4 de mar. de 2022 às 13:56, Khem Raj escreveu:
>>
>> There are recipes in meta-oe and meta-python which would need this
>> and both layer only list core as sole dependency, if we put it in either of
>> these layers, then one
Em sex., 4 de mar. de 2022 às 13:56, Khem Raj escreveu:
> There are recipes in meta-oe and meta-python which would need this
> and both layer only list core as sole dependency, if we put it in either of
> these layers, then one will depend on other which is not nice, so I rather
> would prefer it
On Fri, Mar 4, 2022 at 6:06 AM Konrad Weihmann wrote:
>
>
>
> On 04.03.22 14:13, Ross Burton wrote:
> > On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
> >> For me that would be a candidate to be added to meta-python, or are
> >> there any core recipes that currently break because of the new
On 04.03.22 14:13, Ross Burton wrote:
On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
For me that would be a candidate to be added to meta-python, or are
there any core recipes that currently break because of the new behavior?
This is restoring existing behaviour, so I believe it should
On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
> For me that would be a candidate to be added to meta-python, or are
> there any core recipes that currently break because of the new behavior?
This is restoring existing behaviour, so I believe it should be in
core. There's going to be enough
For me that would be a candidate to be added to meta-python, or are
there any core recipes that currently break because of the new behavior?
Furthermore the variables names are the same, so if people accidentally
(or due to complex injection trees/classes/distro settings/whatever have
new setu
Following a good discussion with PyPA upstream[1] the migration of the
setuptools3.bbclass to use bdist_wheel+pip turns out to be more complex
than thought.
Essentially, we're midway through a lot of changes: the future of Python
packaging is wheels and pip, but those by design are not as flexible
11 matches
Mail list logo
