Open Stack

On Wed, Sep 3, 2014 at 8:21 PM, Doug Hellmann <doug at doughellmann.com> wrote:
>
>  On Sep 3, 2014, at 11:57 AM, Clark Boylan <cboylan at sapwetik.org> wrote:
> > On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote:
> >>
> >> On Sep 2, 2014, at 3:17 PM, Clark Boylan <cboylan at sapwetik.org> wrote:
> >>> The setup.cfg classifiers should be able to do that for us, though PBR
> >>> may need updating? We will also need to learn to upload potentially >1
> >>
> >> How do you see that working? We want all of the Oslo libraries to,
> >> eventually, support both python 2 and 3. How would we use the
> classifiers
> >> to tell when to build a universal wheel and when to build separate
> >> wheels?
> >>
> > The classifiers provide info on the versions of python we support. By
> > default we can build python2 wheel if only 2 is supported, build python3
> > wheel if only 3 is supported, build a universal wheel if both are
> > supported. Then we can add a setup.cfg flag to override the universal
> > wheel default to build both a python2 and python3 wheel instead. Dstufft
> > and mordred should probably comment on this idea before we implement
> > anything.
>
> OK. I’m not aware of any python-3-only projects, and the flag to override
> the universal wheel is the piece I was missing. I think there’s already a
> setuptools flag related to whether or not we should build universal wheels,
> isn’t there?
>

I think we should rely on wheel.universal flag from setup.cfg if it's
there. If it's set, we should always build universal wheels. If it's not
set, we should look in specifiers and build wheels for Python versions that
are mentioned there.

-- 

Kind regards, Yuriy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140904/594a8b23/attachment.html>