Binary wheel distribution?
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
Hi Nathan,
I think this is a great idea. I also now have windows vm resources
here, if that helps. (cc JZH)
-Matt
On Thu, Oct 2, 2014 at 6:21 PM, Nathan Goldbaum
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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I am also pro-wheel. 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@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com
On Oct 2, 2014, at 7:41 PM, Matthew Turk
wrote: Hi Nathan,
I think this is a great idea. I also now have windows vm resources here, if that helps. (cc JZH)
-Matt
On Thu, Oct 2, 2014 at 6:21 PM, Nathan Goldbaum
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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Thu, Oct 2, 2014 at 4:41 PM, Matthew Turk
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.
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
of so-called "binary wheels" (everything in python packaging is a joke about cheese...). The main advantage of wheels is that users installing via
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
On Thu, Oct 2, 2014 at 6:21 PM, Nathan Goldbaum
javascript:_e(%7B%7D,'cvml','nathan12343@gmail.com');> wrote: form pip 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@lists.spacepope.org javascript:_e(%7B%7D,'cvml','yt-dev@lists.spacepope.org'); http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org javascript:_e(%7B%7D,'cvml','yt-dev@lists.spacepope.org'); http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
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@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com
On Oct 2, 2014, at 9:57 PM, Nathan Goldbaum
wrote: On Thu, Oct 2, 2014 at 4:41 PM, Matthew Turk
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
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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
We can potentially get OSX VMs. (Not to be confused with OSX VMS, which
would be the greatest operating system ever.) I'll check into it and get
some accounts.
Matt
On Oct 2, 2014 9:00 PM, "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@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com
On Oct 2, 2014, at 9:57 PM, Nathan Goldbaum
wrote: On Thu, Oct 2, 2014 at 4:41 PM, Matthew Turk
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.
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
of so-called "binary wheels" (everything in python packaging is a joke about cheese...). The main advantage of wheels is that users installing via
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
On Thu, Oct 2, 2014 at 6:21 PM, Nathan Goldbaum
wrote: form pip 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (3)
-
John ZuHone
-
Matthew Turk
-
Nathan Goldbaum