I suspect that many of the maintainers of major scipy-ecosystem projects
are aware of these (or other similar) travis wheel caches, but would guess
that the pool of travis-ci python users who weren't aware of these wheel
caches is much much larger. So there will still be a lot of travis-ci clock
cy
On Thu, Mar 24, 2016 at 11:44 AM, Peter Cock wrote:
> On Thu, Mar 24, 2016 at 6:37 PM, Nathaniel Smith wrote:
>> On Mar 24, 2016 8:04 AM, "Peter Cock" wrote:
>>>
>>> Hi Nathaniel,
>>>
>>> Will you be providing portable Linux wheels aka manylinux1?
>>> https://www.python.org/dev/peps/pep-0513/
>>
On Thu, Mar 24, 2016 at 6:37 PM, Nathaniel Smith wrote:
> On Mar 24, 2016 8:04 AM, "Peter Cock" wrote:
>>
>> Hi Nathaniel,
>>
>> Will you be providing portable Linux wheels aka manylinux1?
>> https://www.python.org/dev/peps/pep-0513/
>
> Matthew Brett will (probably) do the actual work, but yeah,
On Mar 24, 2016 8:04 AM, "Peter Cock" wrote:
>
> Hi Nathaniel,
>
> Will you be providing portable Linux wheels aka manylinux1?
> https://www.python.org/dev/peps/pep-0513/
Matthew Brett will (probably) do the actual work, but yeah, that's the idea
exactly. Note the author list on that PEP ;-)
-n
On Thu, Mar 24, 2016 at 4:04 PM, Peter Cock
wrote:
> Hi Nathaniel,
>
> Will you be providing portable Linux wheels aka manylinux1?
> https://www.python.org/dev/peps/pep-0513/
>
> Does this also open up the door to releasing wheels for SciPy
> too?
>
That should work just fine.
> While speeding
Hi Nathaniel,
Will you be providing portable Linux wheels aka manylinux1?
https://www.python.org/dev/peps/pep-0513/
Does this also open up the door to releasing wheels for SciPy
too?
While speeding up "pip install" would be of benefit in itself,
I am particularly keen to see this for use within
