On Tue, 18 Sep 2018 at 11:51, Joni Orponen wrote:
>
> On Mon, Sep 17, 2018 at 6:07 PM Antoine Pitrou wrote:
>>
>> Paul Moore wrote:
>> > I'm not really familiar with manylinux1, but I'd be concerned if we
>> > started getting bug reports on pip because we installed a library that
>> > claimed to
On Tue, Sep 18, 2018, at 10:02 AM, Antoine Pitrou wrote:
> Nathaniel Smith wrote:
> > It's naughty, you shouldn't do it, and the energy you put into making
> > pseudo-manylinux1 wheels could probably be better put into making finishing
> > up the manylinux2010 work – there's not that much to do.
>
> On Sep 18, 2018, at 8:44 AM, Olivier Grisel wrote:
>
> That's an interesting proposition.
>
> Would pip be able to automatically select the most recent compatible wheel
> when two are available on PyPI?
Yes. Well “recent” isn’t the right way to describe it. Basically when pip is
looking
On Tue, 18 Sep 2018 at 13:45, Olivier Grisel wrote:
>
> > I would say there's value in having two official manylinux flavors at once,
> > for example manylinux2010 for maximum compatibility (it's already 8 years
> > old as far as requirements go!) and manylinux2016 for recent systems
> >
> I would say there's value in having two official manylinux flavors at
once, for example manylinux2010 for maximum compatibility (it's already 8
years old as far as requirements go!) and manylinux2016 for recent systems
compatibility. Later, manylinux2022 gets released as the "recent systems
Nathaniel Smith wrote:
> It's naughty, you shouldn't do it, and the energy you put into making
> pseudo-manylinux1 wheels could probably be better put into making finishing
> up the manylinux2010 work – there's not that much to do.
Can you explain what's missing?
Paul Moore wrote:
> 1. It sounds
On Mon, 17 Sep 2018 at 17:08, Antoine Pitrou wrote:
>
> Paul Moore wrote:
> > I'm not really familiar with manylinux1, but I'd be concerned if we
> > started getting bug reports on pip because we installed a library that
> > claimed to be manylinux1 and was failing because it wasn't. (And yes,
>
On Mon, Sep 17, 2018, 08:25 Antoine Pitrou wrote:
> Hi,
>
> According to recent messages, it seems manylinux2010 won't be ready soon.
> However, the baseline software in manylinux1 is becoming very old. As an
> example, a popular C++ library (Abseil - https://abseil.io/) requires a
> more recent
On Mon, Sep 17, 2018, 18:51 Joni Orponen wrote:
> On Mon, Sep 17, 2018 at 6:07 PM Antoine Pitrou wrote:
>
>> Paul Moore wrote:
>> > I'm not really familiar with manylinux1, but I'd be concerned if we
>> > started getting bug reports on pip because we installed a library that
>> > claimed to be
On Mon, Sep 17, 2018 at 6:07 PM Antoine Pitrou wrote:
> Paul Moore wrote:
> > I'm not really familiar with manylinux1, but I'd be concerned if we
> > started getting bug reports on pip because we installed a library that
> > claimed to be manylinux1 and was failing because it wasn't. (And yes,
>
Paul Moore wrote:
> I'm not really familiar with manylinux1, but I'd be concerned if we
> started getting bug reports on pip because we installed a library that
> claimed to be manylinux1 and was failing because it wasn't. (And yes,
> packaging errors like this are a common source of pip bug
On Mon, Sep 17, 2018 at 11:59 AM Paul Moore wrote:
>
> I'm not really familiar with manylinux1, but I'd be concerned if we
> started getting bug reports on pip because we installed a library that
> claimed to be manylinux1 and was failing because it wasn't. (And yes,
> packaging errors like this
On Mon, 17 Sep 2018 at 16:48, Trishank Kuppusamy
wrote:
>
> On Mon, Sep 17, 2018 at 11:37 AM Antoine Pitrou wrote:
>>
>>
>> Sorry, there was a misunderstanding. Maybe I should have been clearer.
>> My question was about publishing deliberately incompatible manylinux1 wheels
>> (without changing
Trishank Kuppusamy wrote:
> We are looking for help to review manylinux2010, though:
Yes, but I'm not competent for that unfortunately. Sorry :-(
Regards
Antoine.
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
On Mon, Sep 17, 2018 at 11:37 AM Antoine Pitrou wrote:
>
> Sorry, there was a misunderstanding. Maybe I should have been clearer.
> My question was about publishing deliberately incompatible manylinux1
> wheels
> (without changing the PEP).
>
Ah, I see. Hmm, well, I guess this is all right on a
Trishank Kuppusamy wrote:
> I think this will require updating the PEP, at the very least:
Sorry, there was a misunderstanding. Maybe I should have been clearer.
My question was about publishing deliberately incompatible manylinux1 wheels
(without changing the PEP).
Regards
Antoine.
--
On Mon, Sep 17, 2018 at 11:24 AM Antoine Pitrou wrote:
>
> According to recent messages, it seems manylinux2010 won't be ready soon.
> However, the baseline software in manylinux1 is becoming very old. As an
> example, a popular C++ library (Abseil - https://abseil.io/) requires a
> more recent
17 matches
Mail list logo
