This reminds me of something I wanted to ask – how come the "virtualenv"
tool installs wheel but the built-in "venv" tool does not? The latter is
the currently recommended method of creating a virtualenv, isn't it?
27.05.2016, 19:40, Donald Stufft kirjoitti:
On May 27, 2016, at 12:37 PM, Paul Moore <p.f.mo...@gmail.com> wrote:
On 27 May 2016 at 17:28, Chris Barker <chris.bar...@noaa.gov> wrote:
So I kind of like the idea of making wheels the default for distributing on
PyPi always -- even for pure python modules. And wheels are trivial to build
from pure python packages -- so why not?
It would be *really* nice to have some sort of metadata/flag that said
"this project is pure Python". Normally, what I want is not *quite*
--only-binary, but rather "only binary except for pure Python where
I'm happy to take a source distribution". But AFAIK, there's no way
for pip to know that :-(
The flip side is it should be trivial for pure Python projects to release
wheels, often requiring them to do nothing different except ensuring `wheel` is
installed and running ``setup.py sdist bdist_wheel` instead of just `setup.py
sdist`.
—
Donald Stufft
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
