Handling wheels about zest.releaser HOT 6 CLOSED

You're right. I'm not building wheels myself (yet), so I don't have experience with them yet.

You're saying that if there's bdist_wheel in the setup.cfg, is it really only a matter of adding the extra bdist_wheel argument to our call to setup.py?

Or can there be more that needs to be done? Like making different kinds of wheels?

I really should dive into wheel usage. I'm pretty certain I'll like them :-)

from zest.releaser.

You can build specific wheels using command line switches (docs) but I think that is ok to ask zest.releaser users to have a properly designed setup.cfg (That is what everybody will do anyway.)

For pure python packages that are compatible with python 2 and 3 I think the suggested approach is valid (Maybe checking also that says universal = 1) (see here).

For more complex packages (those which includes extensions or that rely on 2to3), it is not clear to me how to do it properly but you can start by supporting simple packages.

from zest.releaser.

It would be great to have wheel support and for first i think its enough for 95% of cases to scan for universal wheel support and do the upload then as described by @hgrecco

from zest.releaser.

I created a pull request for this. It simply runs the bdist_wheel command at the same time as sdist when the wheel package is available. It does not check setup.cfg. I wonder if that is enough initially, or if we should really check if the package has a setup.cfg with a bdist_wheel section, which could be empty.

The advantage of the simple approach in this pull request is that packages need no changes.

Can we think of existing packages where this is a bad idea?
I am not sure how smart bdist_wheel is about autodiscovering that a correct and sane wheel is created.
Might be safer to check for a bdist_wheel entry in setup.cfg. Or possibly add an option for the zest.releaser section.

from zest.releaser.

@mauritsvanrees, you started with a zest.releaser[recommended] list that includes 'wheel' right now. See #49 where you talk about that recommended list.

from zest.releaser.

Is on master and will end up in next release (4.0).

from zest.releaser.