[SciPy-Dev] What we do struggle with is lack of progress on

[Scott Sievert]

👍 to docker. I’d far prefer that if it has clear documentation. It’s far
simpler.

Scott

On January 24, 2018 at 2:49:39 PM, Nathaniel Smith (njs at pobox.com) wrote:

> Yeah, I've tried using AMIs for development, and local VMs are a *way*
> better experience. Much less fiddly copying of files back and forth, better
> latency, etc.
>
> It might make sense to have instructions for getting a docker-based Linux
> development environment spun up quickly on Windows and MacOS – these are
> really popular nowadays so there's quite a bit of infrastructure for making
> it easy.
>
> On Jan 24, 2018 11:13 AM, "Stefan van der Walt" <stefanv at berkeley.edu>
> wrote:
>
>> On Wed, 24 Jan 2018 07:23:01 -0800, Scott Sievert wrote:
>>
>>> I think creating an AMI would be useful. I’ve run into build issues on my
>>> OSX machine and turned to Amazon to build SciPy and run the tests.
>>>
>>
>> This sounds like a fairly cumbersome way to develop.  We already have
>> Travis CI to do the testing in case you really can't compile, and
>> there's always Docker Linux images if you're in a fix.
>>
>> If it were up to me, we'd rather spend energy on updating the developer
>> documentation so that each person can setup their own functioning
>> environment.
>>
>> Stéfan
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180124/b573512a/attachment.html>