out.
-Robert
On Thu, Jan 21, 2016 at 1:03 AM, M.-A. Lemburg <m...@egenix.com> wrote:
>
> Robert McGibbon: Thanks for writing up this PEP :-)
>
> Some comments below...
>
> On 21.01.2016 04:55, Nathaniel Smith wrote:
> > The ``manylinux1`` policy
> > ==
On Thu, Jan 21, 2016 at 1:31 AM, Nick Coghlan wrote:
>
> I think it's better to start with a small core that we *know* works,
> then expand later, rather than trying to make the first iteration too
> wide. The "manylinux1" tag itself is versioned (hence the "1" at the
> end),
i all,
> >
> > Here's a first draft of a PEP for the manylinux1 platform tag
> > mentioned earlier, posted for feedback. Really Robert McGibbon should
> > get the main credit for this, since he wrote it, and also the docker
> > image and the amazing auditwheel tool
It looks like this is a setuptools bug that has been reported upstream [1].
[1]
https://bitbucket.org/pypa/setuptools/issues/464/typeerror-in-install_wrapper_scripts
-Robert
On Tue, Nov 24, 2015 at 2:37 PM, Chris Withers
wrote:
> Looks like it's not isolated to that
But I think dll/pyd files from extension modules present more of a
challenge, since they're left open. I recall some issues around this with
conda (e.g. https://github.com/conda/conda-build/pull/520)
-Robert
On Sun, Nov 15, 2015 at 12:31 PM, Paul Moore wrote:
> On 15
pip in the way it determines the supported pep425 tags. I
think I've confirmed that, and I'll file a PR shortly.
-Robert
On Fri, Nov 6, 2015 at 4:04 PM, Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> On Nov 6, 2015, at 3:57 PM, Robert McGibbon <rmcgi...@gmail.com> wr
rqfcbkwak4rkfkx-t15b_ghmath6raekhqkhx...@mail.gmail.com>,
> Robert McGibbon <rmcgi...@gmail.com> wrote:
> > I just tried to run `pip install numpy` on my OS X 10.10.3 box, and it
> > proceeds to download and compile the tarball from PyPI from source (very
> > slow). I see
Sounds good. I'll take a look.
-Robert
On Fri, Nov 6, 2015 at 11:23 AM, Daniel Holth <dho...@gmail.com> wrote:
> If you would like to fix the problem, figure out how to get the real OSX
> version into pip.pep425tags.
>
> On Fri, Nov 6, 2015 at 2:20 PM Robert McGibbon <rmcg
Hi,
I just tried to run `pip install numpy` on my OS X 10.10.3 box, and it
proceeds to download and compile the tarball from PyPI from source (very
slow). I see, however, that pre-compiled OS X wheel files are available on
PyPI for OS X 10.6 and later.
Checking the code, it looks like pip is
c "import pprint,
> pip.pep425tags; pprint.pprint(pip.pep425tags.get_supported())"
>
> Do none of the tags for the available numpy wheels appear in that list?
>
> On Fri, Nov 6, 2015 at 1:48 PM Robert McGibbon <rmcgi...@gmail.com> wrote:
>
>> Hi,
>>
>&g
what you mean. Sounds like a bug to me.
>
> On Fri, Nov 6, 2015 at 2:07 PM Robert McGibbon <rmcgi...@gmail.com> wrote:
>
>> I don't think it's the sorting, per se. All of the get_supported() tags
>> are 10.5 or earlier. Here's the output:
>> https://gis
Hi,
Thanks for sharing that video, Donald.
In context, I don't think it's fair to characterize the speaker's
perspective as *dangerous*, or of categorically favoring current users over
potential new users. Obviously there are a lot of tradeoffs around backward
compatibility, and no
If you're just after the ability to say I want to include this file in
the sdist, but not in the built wheel file or installed distribution (as I
now believe you are)
I think that you can add the file to the MANIFEST.in file to achieve the
desired behavior.
-Robert
On Sun, Jan 18, 2015 at
13 matches
Mail list logo