release wheels.

[graingert]

No description provided.

[techtonik]

Why wheels? The code is binary independent, so no wheels are required..

[graingert]

http://pythonwheels.com/

1. Faster installation for pure python and native C extension packages.
2. Avoids arbitrary code execution for installation. (Avoids setup.py)
3. Installation of a C extension does not require a compiler on Windows or OS X.
4. Allows better caching for testing and continuous integration.
5. Creates .pyc files as part of installation to ensure they match the python interpreter used.
6. More consistent installs across platforms and machines.

[graingert]

wheels shave a few seconds off of everyone's build. I'm not going to add any non-wheel packages to my CI builds. And many people will avoid depending on patch because of it.

[techtonik]

Thanks for the info. I don't think that there is big win in speed, but I agree that getting rid of setup.py is a big deal. Caching can be a problem.

What does mean "more consistent" - I thought that it is either not consistent or consistent. What do they mean?

[techtonik]

But current .zip files are executable. You don't even need to install them to use. =(

[graingert]

And also you need to know, that I was expelled from Python community, because I didn't want to follow the lemmings way as I put it.

I consider myself a member of this community. Thanks for pointing this out. Maybe you should add this to your README.md?

[techtonik]

@graingert sorry, didn't want to discourage you, it is all health problems, the lack of employment and money that make me mean. If you want a deeper discussion with problems with Python ecosystem and economics and a ways to fix that, you can always ping me.

wheels is still an awesome feature, regardless of human issues.

[techtonik]

If Tidelift approves this package for subscription, I will look into altering pypack to produce wheels instead of intermediate .zip files.

[pombredanne]

@techtonik any plan for doing this after all? Thank you.