Python packaging: wheels vs tarball (tar.gz) -
the advantage of wheels on eggs clear (see section why not egg? https://pypi.python.org/pypi/wheel).
however, not entirely clear me advantage of using wheels on tar.gz
. might missing obvious "they same". see both can installed directly using pip
(even in windows), have similar size , when packaging require similar effort. sounds me kind of questions might when justifying packaging methodology.
edit: found example tar.gz
might better wheels. cherrypy (https://pypi.python.org/pypi/cherrypy) provides wheels python 3.x only, if want have local repository serve cherrypy python 2.7 , 3.x dependencies, seems make more sense store tarball. correct? (just add couple of "case-based" justification discussion)
this answered me (directly wheel pep):
python needs package format easier install sdist. python's sdist packages defined , require distutils , setuptools build systems, running arbitrary code build-and-install, , re-compile, code can installed new virtualenv. system of conflating build-install slow, hard maintain, , hinders innovation in both build systems , installers.
wheel attempts remedy these problems providing simpler interface between build system , installer. wheel binary package format frees installers having know build system, saves time amortizing compile time on many installations, , removes need install build system in target environment.
https://www.python.org/dev/peps/pep-0427/#rationale
note tarballs we're speaking of referred "sdists" above.
Comments
Post a Comment