[yt-dev] Binary wheel distribution?

[John ZuHone]

I tried spinning up something on Appveyor, but it turns out that you only get like 30 min sessions for free or something like that. Not enough time for compiling the latest version and running the tests. 

I had mentioned to Matt about seeing if I could get a login on those Windows resources.

John ZuHone
Kavli Center for Astrophysics and Space Research
Massachusetts Institute of Technology
77 Massachusetts Ave., 37-582G
Cambridge, MA 02139
(w) 617-253-2354
(m) 781-708-5004
jzuhone at space.mit.edu
jzuhone at gmail.com
http://www.jzuhone.com

> On Oct 2, 2014, at 9:57 PM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
> 
> 
> 
>> On Thu, Oct 2, 2014 at 4:41 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>> Hi Nathan,
>> 
>> I think this is a great idea.  I also now have windows vm resources
>> here, if that helps.  (cc JZH)
>> 
>> -Matt
> 
> I was going to look into Appveyor, but this works as well!  I'll contact you about this once I get the tooling set up on Appveyor.
> 
> Do you have access OS X VMs? I have spare mac minis sitting around, but that's not really sustainable for after I leave UCSC.
>  
>> 
>> On Thu, Oct 2, 2014 at 6:21 PM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
>> > Hi all,
>> >
>> > Recently the python packaging ecosystem has come up with a new way of
>> > sharing binary builds of python packages to end users.  This takes the form
>> > of so-called "binary wheels" (everything in python packaging is a joke about
>> > cheese...).  The main advantage of wheels is that users installing via pip
>> > on Windows and OSX will no longer need compilers to build yt and
>> > installation will also proceed significantly faster. As far as I can tell,
>> > wheels are discouraged on Linux since it's assumed that users will use their
>> > OS package manager to install binary builds. You may even be using wheels
>> > right now - matplotlib, numpy, and many other projects with c extensions are
>> > now distributing wheels on OS X and windows. More information about wheels
>> > is available here:
>> >
>> > http://wheel.readthedocs.org/en/latest/
>> > https://python-packaging-user-guide.readthedocs.org/en/latest/
>> >
>> > The main downside of wheels is that it's another piece of tooling to
>> > maintain.
>> >
>> > I just tested and with a newish version of setuptools and the "wheel"
>> > package installed, our setup script can produce wheels!  You just need to do
>> > "python setup.py bdist_wheel".
>> >
>> > I'm curious whether people would be agreeable in principle to uploading
>> > wheels to PyPI as a (semi-)automated part of our release process.  Please
>> > let me know what you think.
>> >
>> > -Nathan
>> >
>> > _______________________________________________
>> > yt-dev mailing list
>> > yt-dev at lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> 
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20141002/33720cc1/attachment.html>