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 m
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,
>
echo 2 > /sys/kernel/debug/x86/ibrs_enabled
(Coss-posting to distutils-sig, as C extensions may be the most likely
abuse vector)
# Forwarded message
From: Wes Turner
Date: Mon, Sep 17, 2018 at 3:41 PM
Subject: Re: SEC: Spectre variant 2: GCC: -mindirect-branch=thunk
-mindirect-branch-register
C
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 report
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 t
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
https://mail
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.
--
Distutils
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 g
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 glibc (see
https://github.com/abseil/abseil-cpp/commit/add8
On Monday, September 17, 2018, Paul Moore wrote:
> On Sun, 16 Sep 2018 at 15:08, Nick Coghlan wrote:
>
> > So if folks are still interested in the general idea of improving
> virtualenv and venv interoperability, then my last message to that thread
> and Paul's follow up would be a decent place
Hello,
We have a few issues in tox that are essentially upstream bugs inside
virtualenv. Hence, why I proposed myself to become a maintainer of
virtualenv. I feel like tox is probably one of the bigger user bases out
there. The first order of business would definitely be improving the CI and
looki
On Sun, 16 Sep 2018 at 15:08, Nick Coghlan wrote:
> So if folks are still interested in the general idea of improving virtualenv
> and venv interoperability, then my last message to that thread and Paul's
> follow up would be a decent place to start:
> https://github.com/pypa/virtualenv/pull/6
15 matches
Mail list logo
