Hi all,
I think Nathaniel raised a lot of important points below and I do see the
case for a "base environment" meta tag. The implementation of sniffing out
those environments on a wide array of systems may be complicated, but
perhaps we can, er, borrow from conda here. I do think the glibc tag
On Tue, Sep 8, 2015 at 10:10 PM, Nathaniel Smith wrote:
> On Mon, Sep 7, 2015 at 9:02 AM, Donald Stufft wrote:
> > On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> >> >>>
> >> >>> I'll create PRs for this against wheel and pip shortly.
On Wed, Sep 9, 2015 at 8:06 AM, Nate Coraor wrote:
> On Tue, Sep 8, 2015 at 10:10 PM, Nathaniel Smith wrote:
>>
>> On Mon, Sep 7, 2015 at 9:02 AM, Donald Stufft wrote:
>> > On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu)
Hi,
Going back in time to this old post, but I think it becomes more relevant
now that Nate's work is being completed:
On 13 August 2015 at 22:47, Nathaniel Smith wrote:
> On Thu, Aug 13, 2015 at 12:30 PM, Leonardo Rochael Almeida
> wrote:
> >
> > On 13
On Sep 8, 2015 1:33 PM, "Donald Stufft" wrote:
>
> On September 8, 2015 at 1:29:53 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> > On Mon, Sep 7, 2015 at 12:02 PM, Donald Stufft wrote:
> >
> > > On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu)
wrote:
> > > > >>>
>
https://www.python.org/dev/peps/pep-0425/#platform-tag is currently defined
in terms of distutils get_platform(). Instead, it could be defined more
abstractly to read something like "The platform tag expresses which
system(s) might be capable of running or linking with binary components of
the
That's nice for singling out some packages (though I only found a , but I
had a different use-case in mind, which I guess I didn't fully articulate:
I might want binary wheels for some packages, just not coming from PyPI,
where I don't necessarily trust whatever was put there. I'm perfectly fine
On Mon, Sep 7, 2015 at 9:02 AM, Donald Stufft wrote:
> On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu) wrote:
>> >>>
>> >>> I'll create PRs for this against wheel and pip shortly. I can also work
>> >>> on a PEP for the platform tag - I don't think it's going
On Mon, Sep 7, 2015 at 12:02 PM, Donald Stufft wrote:
> On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> > >>>
> > >>> I'll create PRs for this against wheel and pip shortly. I can also
> work
> > >>> on a PEP for the platform tag - I don't think it's
On September 8, 2015 at 1:29:53 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> On Mon, Sep 7, 2015 at 12:02 PM, Donald Stufft wrote:
>
> > On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> > > >>>
> > > >>> I'll create PRs for this against wheel and pip shortly. I can also
>
I'm still unclear on whether you'd want A or B:
A) Different major/minor versions of the spec are different documents
B) Different versions of the spec are tags or branches of the same document
If it's B, then you'd either:
1) only build the latest version, and construct an index of links to the
On September 3, 2015 at 1:23:03 PM, Nate Coraor (n...@bx.psu.edu) wrote:
> >>>
> >>> I'll create PRs for this against wheel and pip shortly. I can also work
> >>> on a PEP for the platform tag - I don't think it's going to need to be a
> >>> big one. Are there any preferences as to whether this
MAJOR.MINOR.PATCH[-rev] would be helpful for these (and other) PEPs.
On Sep 7, 2015 10:36 AM, "Marcus Smith" wrote:
>
> I'm still unclear on whether you'd want A or B:
>
> A) Different major/minor versions of the spec are different documents
>From http://semver.org Semantic
Wes, this isn't about the versioning scheme for Specs or PEPS.
For *whatever* scheme we have, my discussion was about how to render all
the "current" versions we support in a Sphinx project.
in short, should the current versions we want to publish be distinct
documents or not.
> The PEP
On Sep 7, 2015 12:51 PM, "Marcus Smith" wrote:
>
> Wes, this isn't about the versioning scheme for Specs or PEPS.
> For *whatever* scheme we have, my discussion was about how to render all
the "current" versions we support in a Sphinx project.
More or less itertools.product
On 8 September 2015 at 01:36, Marcus Smith wrote:
> I'm still unclear on whether you'd want A or B:
>
> A) Different major/minor versions of the spec are different documents
> B) Different versions of the spec are tags or branches of the same document
I'm mainly thinking A,
Nick Coghlan writes:
> On 7 September 2015 at 02:09, Marcus Smith wrote:
> > For example, down the road when there's Wheel 2.0, what's the "Current
> > Specs" for wheel?
>
> Yes, but I think that's easy enough to handle by having a default URL
> that always
> That way, the URL works as people expect, *and* the resulting
> > destination gives a URL that (when inevitably copy-and-pasted) will
> > retain its meaning over time.
>
> Yes, ReadTheDocs does let us do that.
well, it lets you do it for a whole project.
we'd have to have a project per spec
On 7 September 2015 at 14:11, Marcus Smith wrote:
>
>
>> > That way, the URL works as people expect, *and* the resulting
>> > destination gives a URL that (when inevitably copy-and-pasted) will
>> > retain its meaning over time.
>>
>> Yes, ReadTheDocs does let us do that.
>
>
>
On 7 September 2015 at 02:09, Marcus Smith wrote:
> One thought that comes to mind is how to present specs that deal with
> formats and artifacts that persist for years.
>
> For example, down the road when there's Wheel 2.0, what's the "Current
> Specs" for wheel?
>
> I would
On 7 September 2015 at 09:42, Ben Finney wrote:
> Nick Coghlan writes:
>
>> On 7 September 2015 at 02:09, Marcus Smith wrote:
>> > For example, down the road when there's Wheel 2.0, what's the "Current
>> > Specs" for wheel?
>>
One thought that comes to mind is how to present specs that deal with
formats and artifacts that persist for years.
For example, down the road when there's Wheel 2.0, what's the "Current
Specs" for wheel?
I would describe 2.0 is the "Latest" spec, but "Current Specs" includes all
versions we're
On 5 September 2015 at 16:46, Nathaniel Smith wrote:
> On Fri, Sep 4, 2015 at 9:24 PM, Marcus Smith wrote:
>>> I don't have a specific problem with the specs living somewhere else
>>> as well, I just don't think moving a lengthy document full of edge cases
>>>
On 5 September 2015 at 14:24, Marcus Smith wrote:
>> I don't have a specific problem with the specs living somewhere else
>> as well, I just don't think moving a lengthy document full of edge cases
>> from one location to another is going to make things better
>
> If I may, I
On Fri, Sep 4, 2015 at 9:24 PM, Marcus Smith wrote:
>> I don't have a specific problem with the specs living somewhere else
>> as well, I just don't think moving a lengthy document full of edge cases
>> from one location to another is going to make things better
>
> If I may, I
On 5 September 2015 at 16:43, Nick Coghlan wrote:
> On 5 September 2015 at 14:24, Marcus Smith wrote:
>>> I don't have a specific problem with the specs living somewhere else
>>> as well, I just don't think moving a lengthy document full of edge cases
>>>
> I don't have a specific problem with the specs living somewhere else
> as well, I just don't think moving a lengthy document full of edge cases
> from one location to another is going to make things better
If I may, I don't think that really captures Nick's idea.
I think it's about clearly
On September 4, 2015 at 10:12:08 PM, Nick Coghlan (ncogh...@gmail.com) wrote:
> On 3 September 2015 at 09:45, Donald Stufft wrote:
> > On September 1, 2015 at 9:57:50 AM, Daniel Holth (dho...@gmail.com) wrote:
> >> Looks amazing, why don't we merge it.
> >>
> >
> > I think we need to update the
On 5 September 2015 at 12:14, Donald Stufft wrote:
> On September 4, 2015 at 10:12:08 PM, Nick Coghlan (ncogh...@gmail.com) wrote:
>> It's only the interoperability specs where we currently follow the RFC
>> model of having the same document describe both the end result *and*
>>
On September 4, 2015 at 10:56:38 PM, Nick Coghlan (ncogh...@gmail.com) wrote:
> On 5 September 2015 at 12:14, Donald Stufft wrote:
> > On September 4, 2015 at 10:12:08 PM, Nick Coghlan (ncogh...@gmail.com)
> > wrote:
> >> It's only the interoperability specs where we currently follow the RFC
> >>
On 3 September 2015 at 09:45, Donald Stufft wrote:
> On September 1, 2015 at 9:57:50 AM, Daniel Holth (dho...@gmail.com) wrote:
>> Looks amazing, why don't we merge it.
>>
>
> I think we need to update the PEP or write a new PEP before we add new tags
> to the implementation.
On Thu, Sep 3, 2015 at 8:16 AM, Donald Stufft wrote:
> On September 3, 2015 at 8:15:53 AM, Daniel Holth (dho...@gmail.com) wrote:
> > We could at least merge the implementation of the SOABI tag for Python
> 2.7
> > (cp27m, cp27mu, ...), which has been in the PEP from the
IIRC there's also a bug where we use pypy's version "2.6.2" and not the
version of Python it implements "2.7" for the first tag.
On Thu, Sep 3, 2015 at 9:53 AM Nate Coraor wrote:
> On Thu, Sep 3, 2015 at 8:16 AM, Donald Stufft wrote:
>
>> On September 3, 2015
On Thu, Sep 3, 2015 at 9:56 AM, Daniel Holth wrote:
> IIRC there's also a bug where we use pypy's version "2.6.2" and not the
> version of Python it implements "2.7" for the first tag.
>
It's the other way around:
https://github.com/pypa/pip/issues/2882
My changes set the
On Thu, Sep 3, 2015 at 10:04 AM, Nate Coraor wrote:
> On Thu, Sep 3, 2015 at 9:56 AM, Daniel Holth wrote:
>
>> IIRC there's also a bug where we use pypy's version "2.6.2" and not the
>> version of Python it implements "2.7" for the first tag.
>>
>
> It's the
We could at least merge the implementation of the SOABI tag for Python 2.7
(cp27m, cp27mu, ...), which has been in the PEP from the beginning but was
never implemented for Python 2. This lets you distinguish between wheels
built for CPython with debug, pymalloc, unicode builds.
For pypy which
On September 3, 2015 at 8:15:53 AM, Daniel Holth (dho...@gmail.com) wrote:
> We could at least merge the implementation of the SOABI tag for Python 2.7
> (cp27m, cp27mu, ...), which has been in the PEP from the beginning but was
> never implemented for Python 2. This lets you distinguish between
On September 1, 2015 at 9:57:50 AM, Daniel Holth (dho...@gmail.com) wrote:
> Looks amazing, why don't we merge it.
>
I think we need to update the PEP or write a new PEP before we add new tags to
the implementation.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356
Looks amazing, why don't we merge it.
On Thu, Aug 27, 2015 at 3:24 PM Nate Coraor wrote:
> On Tue, Aug 25, 2015 at 1:54 PM, Nate Coraor wrote:
>
>> I've started down this road of Linux platform detection, here's the work
>> so far:
>>
>>
On Tue, Aug 25, 2015 at 1:54 PM, Nate Coraor n...@bx.psu.edu wrote:
I've started down this road of Linux platform detection, here's the work
so far:
https://bitbucket.org/natefoo/wheel/src/tip/wheel/platform/linux.py
I'm collecting distribution details here:
I've started down this road of Linux platform detection, here's the work so
far:
https://bitbucket.org/natefoo/wheel/src/tip/wheel/platform/linux.py
I'm collecting distribution details here:
https://gist.github.com/natefoo/814c5bf936922dad97ff
One thing to note, although it's not used,
On Tue, Aug 25, 2015 at 12:54 PM, Nate Coraor n...@bx.psu.edu wrote:
I've started down this road of Linux platform detection, here's the work
so far:
https://bitbucket.org/natefoo/wheel/src/tip/wheel/platform/linux.py
IDK whether codecs.open(file, 'r', encoding='utf8') is necessary or
On Fri, Aug 21, 2015 at 2:51 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 21 August 2015 at 05:58, Robert Collins robe...@robertcollins.net
wrote:
On 21 August 2015 at 07:25, Donald Stufft don...@stufft.io wrote:
On August 20, 2015 at 3:23:09 PM, Daniel Holth (dho...@gmail.com)
wrote:
On Mon, Aug 24, 2015 at 10:03 AM, Nate Coraor n...@bx.psu.edu wrote:
On Fri, Aug 21, 2015 at 2:51 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 21 August 2015 at 05:58, Robert Collins robe...@robertcollins.net
wrote:
On 21 August 2015 at 07:25, Donald Stufft don...@stufft.io wrote:
On
On Mon, Aug 24, 2015 at 1:51 PM, Wes Turner wes.tur...@gmail.com wrote:
On Mon, Aug 24, 2015 at 10:03 AM, Nate Coraor n...@bx.psu.edu wrote:
On Fri, Aug 21, 2015 at 2:51 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 21 August 2015 at 05:58, Robert Collins robe...@robertcollins.net
wrote:
On Fri, Aug 14, 2015 at 3:38 AM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:27 PM, Robert Collins
robe...@robertcollins.net wrote:
On 14 August 2015 at 14:14, Nathaniel Smith n...@pobox.com wrote:
...
Of course if you have an alternative proposal than I'm all ears
On Thu, Aug 20, 2015 at 3:14 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Thu, 20 Aug 2015 14:26:44 -0400
Nate Coraor n...@bx.psu.edu wrote:
So I need a bit of guidance here. I've arbitrarily chosen some tags -
`rhel` for example - and wonder if, like PEP 425's mapping of Python
On Thu, 20 Aug 2015 15:40:57 -0400
Nate Coraor n...@bx.psu.edu wrote:
In practice, the `platform` module does not really keep up to date with
evolution in the universe of Linux distributions.
Understandable, although so far it's doing a pretty good job:
Hmm, perhaps that one just
On Thu, Aug 13, 2015 at 7:27 PM, Robert Collins
robe...@robertcollins.net wrote:
On 14 August 2015 at 14:14, Nathaniel Smith n...@pobox.com wrote:
...
Of course if you have an alternative proposal than I'm all ears :-).
Yeah :)
So, I want to dedicate some time to contributing to this
On 14Aug2015 0038, Nathaniel Smith wrote:
Windows and OS X don't (reliably) have any package manager. So PyPI
*is* inevitably going to contain non-Python shared libraries or
statically linked modules or something like that. (And in fact it
already contains such things today.) I'm not sure what
On Fri, Aug 14, 2015 at 9:17 AM, Steve Dower steve.do...@python.org wrote:
I actually like two ideas for Windows (not clear to me how well they apply
on other platforms),
I think this same approach should be used for OS-X, not sure about Linux --
on LInux, you normally have normal ways to get
On 8/14/2015 16:16, Chris Barker wrote:
On Fri, Aug 14, 2015 at 9:17 AM, Steve Dower steve.do...@python.org
mailto:steve.do...@python.org wrote:
There was discussion about an incompatible_with metadata item at
one point. Could numpy include {incompatible_with: scipyx.y} in
such a
On Wed, Aug 12, 2015 at 6:05 PM, Nathaniel Smith n...@pobox.com wrote:
(2) the special hard-coded tag centos5. (That's what everyone actually
uses in practice, right?)
Is LSB a fantasy that never happened? I haven't followed it for years
-CHB
Compare with osx, where there are actually a
On Thu, Aug 13, 2015 at 10:52 AM, David Cournapeau courn...@gmail.com
wrote:
So this is a basic list I got w/ a few minutes of scripting,
could we define this list (or somethign like it) as
Python-Linux-Standard-Base-version X.Y
Then we have a tag to use on binary wheels, and clearly defined
On Wed, Aug 12, 2015 at 9:05 PM, Nathaniel Smith n...@pobox.com wrote:
On Aug 12, 2015 13:57, Nate Coraor n...@bx.psu.edu wrote:
Hello all,
I've implemented the wheel side of Nick's suggestion from very early in
this thread to support a vendor-providable binary-compatibility.cfg.
On Aug 12, 2015 13:57, Nate Coraor n...@bx.psu.edu wrote:
Hello all,
I've implemented the wheel side of Nick's suggestion from very early in
this thread to support a vendor-providable binary-compatibility.cfg.
https://bitbucket.org/pypa/wheel/pull-request/54/
If this is acceptable, I'll
On Thu, Aug 13, 2015 at 2:05 AM, Nathaniel Smith n...@pobox.com wrote:
On Aug 12, 2015 13:57, Nate Coraor n...@bx.psu.edu wrote:
Hello all,
I've implemented the wheel side of Nick's suggestion from very early in
this thread to support a vendor-providable binary-compatibility.cfg.
On Aug 13, 2015 9:14 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 6:31 PM, Robert Collins
robe...@robertcollins.net wrote:
On 14 August 2015 at 13:25, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:07 AM, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug
On Aug 13, 2015 9:33 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 6:50 PM, Wes Turner wes.tur...@gmail.com wrote:
So, there would be a capability / osnamestr mapping, or just [...]?
Because my libc headers are different.
Hi Wes,
From the question mark I infer that
On Thu, Aug 13, 2015 at 6:50 PM, Wes Turner wes.tur...@gmail.com wrote:
So, there would be a capability / osnamestr mapping, or just [...]?
Because my libc headers are different.
Hi Wes,
From the question mark I infer that this is intended as a question for
me, but like most of your posts I
On Thu, Aug 13, 2015 at 10:52 AM, David Cournapeau courn...@gmail.com wrote:
On Thu, Aug 13, 2015 at 2:05 AM, Nathaniel Smith n...@pobox.com wrote:
On Aug 12, 2015 13:57, Nate Coraor n...@bx.psu.edu wrote:
Hello all,
I've implemented the wheel side of Nick's suggestion from very early
On Thu, Aug 13, 2015 at 6:31 PM, Robert Collins
robe...@robertcollins.net wrote:
On 14 August 2015 at 13:25, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:07 AM, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug 12, 2015 at 9:05 PM, Nathaniel Smith n...@pobox.com wrote:
From my
On 14 August 2015 at 13:25, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:07 AM, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug 12, 2015 at 9:05 PM, Nathaniel Smith n...@pobox.com wrote:
From my reading of what the Enthought and Continuum folks were saying
about how they are
On Aug 13, 2015 8:31 PM, Robert Collins robe...@robertcollins.net wrote:
On 14 August 2015 at 13:25, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:07 AM, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug 12, 2015 at 9:05 PM, Nathaniel Smith n...@pobox.com wrote:
From my
On 14 August 2015 at 13:38, Wes Turner wes.tur...@gmail.com wrote:
On Aug 13, 2015 8:31 PM, Robert Collins robe...@robertcollins.net wrote:
On 14 August 2015 at 13:25, Nathaniel Smith n...@pobox.com wrote:
On Thu, Aug 13, 2015 at 7:07 AM, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug 12,
On Thu, Aug 13, 2015 at 12:30 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
On 13 August 2015 at 11:07, Nate Coraor n...@bx.psu.edu wrote:
On Wed, Aug 12, 2015 at 9:05 PM, Nathaniel Smith n...@pobox.com wrote:
[...]
(2) the special hard-coded tag centos5. (That's what everyone
Hello all,
I've implemented the wheel side of Nick's suggestion from very early in
this thread to support a vendor-providable binary-compatibility.cfg.
https://bitbucket.org/pypa/wheel/pull-request/54/
If this is acceptable, I'll add support for it to the pip side. What else
should be
I'm not sure what will be needed to get the PR accepted; At PyCon AU
Tennessee Leuwenberg started drafting a PEP for the expression of
dependencies on e.g. BLAS - its been given number 497, and is in the
packaging-peps repo; I'm working on updating it now.
On 13 August 2015 at 08:21, Nate Coraor
On Fri, 24 Jul 2015 at 19:53 Chris Barker chris.bar...@noaa.gov wrote:
On Tue, Jul 21, 2015 at 9:38 AM, Oscar Benjamin
oscar.j.benja...@gmail.com wrote:
I think it would be great to just package these up as wheels and put them
on PyPI.
that's the point -- there is no way with the
On Jul 28, 2015 10:02 AM, Oscar Benjamin oscar.j.benja...@gmail.com
wrote:
On Fri, 24 Jul 2015 at 19:53 Chris Barker chris.bar...@noaa.gov wrote:
On Tue, Jul 21, 2015 at 9:38 AM, Oscar Benjamin
oscar.j.benja...@gmail.com wrote:
I think it would be great to just package these up as wheels
On 21 July 2015 at 04:37, Paul Moore p.f.mo...@gmail.com wrote:
On 20 July 2015 at 18:37, Chris Barker chris.bar...@noaa.gov wrote:
sure -- but isn't that use-case already supported by wheel -- define your
own wheelhouse that has the ABI you know you need, and point pip to it.
I presume the
Hi all,
Thanks for the lively debate - I sent the message to start the thread and
then had a week's vacation - and I appreciate the discussion that took
place in the interim. I've encountered all of the problems discussed here,
especially the dependencies both with Python and other attempts at
On Tue, Jul 21, 2015 at 9:38 AM, Oscar Benjamin oscar.j.benja...@gmail.com
wrote:
I think it would be great to just package these up as wheels and put them
on PyPI.
that's the point -- there is no way with the current spec to specify a
wheel dependency as opposed to a package dependency. i.e
Hi Tres,
On 21 July 2015 at 00:25, Tres Seaver tsea...@palladion.com wrote:
[...]
Even given the over-specified platform tags Nick suggests, linux wheels
won't fully work, because the build-time depes won't be satisfiable *by
pip*: the burden will be on each project to attempt a build and
On Fri, 17 Jul 2015 at 16:37 Chris Barker chris.bar...@noaa.gov wrote:
TL;DR -- pip+wheel needs to address the non-python dependency issue before
it can be a full solution for Linux (or anything else, really)
snip
- Packages with semi-standard dependencies: can we expect ANY Linux
distro
On 20 July 2015 at 11:42, Leonardo Rochael Almeida leoroch...@gmail.com wrote:
To solve this problem, so far we've only been able to come up with two
extremes:
- Have the libraries contain enough metadata in their source form that we
can generate true system packages from them (this doesn't
On 20 July 2015 at 18:37, Chris Barker chris.bar...@noaa.gov wrote:
sure -- but isn't that use-case already supported by wheel -- define your
own wheelhouse that has the ABI you know you need, and point pip to it.
I presume the issue is wanting to have a single shared wheelhouse for
a
On Sun, Jul 19, 2015 at 11:00 PM, Nick Coghlan ncogh...@gmail.com wrote:
However, Nate has a specific concrete problem in needing to get
artifacts from Galaxy's build servers and installing them into their
analysis environments - let's help him solve that, on the assumption
that some *other*
On Sun, Jul 19, 2015 at 10:50 PM, Nick Coghlan ncogh...@gmail.com wrote:
The intended use case is Build once, deploy many times.
This is especially important for use cases like Nate's - Galaxy has
complete control over both the build environment and the deployment
environment, but they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2015 11:46 AM, Antoine Pitrou wrote:
Due to the fact Linux binary wheels don't exist, conda is even more
useful on Linux...
FWIW, they exist, they just can't be published to PyPI. Private indexes
(where binary compatibility is a known
Hi,
On 17 July 2015 at 05:22, Nick Coghlan ncogh...@gmail.com wrote:
On 17 July 2015 at 03:41, Nate Coraor n...@bx.psu.edu wrote:
[...]
As mentioned in the wheels PR, there are some questions and decisions
made
that I need guidance on:
- On Linux, the distro name/version (as
On 18 July 2015 at 01:36, Chris Barker chris.bar...@noaa.gov wrote:
TL;DR -- pip+wheel needs to address the non-python dependency issue before
it can be a full solution for Linux (or anything else, really)
The long version:
I think Linux wheel support is almost useless unless the pypa stack
On 18 Jul 2015, at 1:53 am, Chris Barker chris.bar...@noaa.gov wrote:
On Fri, Jul 17, 2015 at 8:46 AM, Antoine Pitrou solip...@pitrou.net wrote:
Due to the fact Linux binary wheels don't exist, conda is even more
useful on Linux...
True -- though it's at least possible, and certainly
On 18 July 2015 at 02:13, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
Someone needs to write that specification. Propose we forget about Windows
for the first revision, so that it is possible to get it done.
If we want Windows support in the long run -- and we do -- we should
be
On 17 July 2015 at 03:41, Nate Coraor n...@bx.psu.edu wrote:
Hi all,
I've recently been working on adding SOABI support for Python 2.x and other
pieces needed to get wheels w/ C extensions for Linux working. Here's the
work for wheels:
https://bitbucket.org/pypa/wheel/pull-request/54/
TL;DR -- pip+wheel needs to address the non-python dependency issue before
it can be a full solution for Linux (or anything else, really)
The long version:
I think Linux wheel support is almost useless unless the pypa stack
provides _something_ to handle non-python dependencies.
1) Pure Python
On Fri, 17 Jul 2015 08:36:39 -0700
Chris Barker chris.bar...@noaa.gov wrote:
- Packages with non-standard non-python dependencies: libhdf5, lapack,
BLAS, fortran(!) -- this is where the nightmare really is. I suspect most
folks on this list will say that this is Scipy Problem, and indeed,
I think Linux wheel support is almost useless unless the pypa stack
provides _something_ to handle non-python dependencies.
I wouldn't say useless, but I tend to agree with this sentiment.
I'm thinking the only way to really compete with the ease of Conda (for
non-python dependencies) is to
On Fri, Jul 17, 2015 at 8:46 AM, Antoine Pitrou solip...@pitrou.net wrote:
Due to the fact Linux binary wheels don't exist, conda is even more
useful on Linux...
True -- though it's at least possible, and certainly easier than on Mac and
Windows, to build it all yourself on Linux.
-CHB
--
2015-07-17 18:50 GMT+02:00 Marcus Smith qwc...@gmail.com:
I think Linux wheel support is almost useless unless the pypa stack
provides _something_ to handle non-python dependencies.
I wouldn't say useless, but I tend to agree with this sentiment.
I'm thinking the only way to really
I've recently packaged SDL2 for Windows as a wheel, without any Python
code. It is a conditional dependency if Windows for a SDL wrapper. Very
convenient. It uses a little WAF script instead of bdist_wheel to make the
package. https://bitbucket.org/dholth/sdl2_lib/src/tip
We were talking on this
Yes, but how do you know that I compiled against the right version of libc?
On Fri, Jul 17, 2015, 9:13 PM Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Jul 17, 2015, at 1:19 PM, Daniel Holth dho...@gmail.com wrote:
I've recently packaged SDL2 for Windows as a wheel, without
On Jul 17, 2015, at 1:19 PM, Daniel Holth dho...@gmail.com wrote:
I've recently packaged SDL2 for Windows as a wheel, without any Python code.
It is a conditional dependency if Windows for a SDL wrapper.
Cool, though I still think we need wheel-level deps -- the dependency
is on the
Hi all,
I've recently been working on adding SOABI support for Python 2.x and other
pieces needed to get wheels w/ C extensions for Linux working. Here's the
work for wheels:
https://bitbucket.org/pypa/wheel/pull-request/54/
Based on that, I've added support for those wheels to pip here:
94 matches
Mail list logo