On Monday 10 February 2014 19:02:55 Doug Hellmann wrote: > On Mon, Feb 10, 2014 at 1:14 PM, Joe Gordon <joe.gord...@gmail.com> wrote: > > On Mon, Feb 10, 2014 at 9:00 AM, Doug Hellmann > > > > <doug.hellm...@dreamhost.com> wrote: > > > On Sat, Feb 8, 2014 at 7:08 PM, Monty Taylor <mord...@inaugust.com> > > > > wrote: > > >> Hey all! > > >> > > >> There are a bunch of patches adding: > > >> > > >> [wheel] > > >> universal = 1 > > >> > > >> to setup.cfg: > > >> > > >> https://review.openstack.org/#/q/status:open+topic:wheel-publish,n,z > > >> > > >> I wanted to follow up on what the deal is with them, and what I think > > >> we > > >> should do about them. > > >> > > >> universal means that a wheel can be made that can work with any python. > > >> That's awesome, and we want it - it makes the wheel publishing code > > > > easier. > > > > >> I don't think we want it turned on for any project that doesn't, in > > > > fact, > > > > >> support python3 - because we'd be producing a wheel that says it works > > > > in > > > > >> python3. > > >> > > >> To be fair - the wheel itself will work just fine in python3 - it's > > >> just > > >> the software that doesn't - and we upload tarballs right now which > > >> don't > > >> block attempts to use them in python3. > > >> > > >> SO - > > >> > > >> my pedantic side says: > > >> > > >> "Let's only land universal = 1 into python3 supporting projects" > > >> > > >> upon further reflection, I think my other side says: > > >> > > >> "It's fine, let's land it everywhere, it doesn't hurt anything, and > > >> then > > >> we can stop worrying about it" > > >> > > >> Thoughts? > > > > > > Do we have any non-library projects that support python 3? > > > > yes, python-novaclient and many more > > > > https://wiki.openstack.org/wiki/Python3 > > OK, the clients always register with me as "libraries" even though they > include the command line programs. > > Are we publishing wheels for any of the service apps where python 3 is not > supported? > > It seems safe to just go ahead and use the universal flag, but how much > work is it to be "correct" and only set the flags for projects that are > actually universal?
It depends what is viewed "actually universal". If the codebase is valid py3k code or if it actually works. As in all deps are ready. I guess a first step would be to bring the python3 status page up-to-date and keep that in sync with "universal" wheels. > What are the ramifications of not using the flag > everywhere? We wouldn't be ultra-correct and have to track this. But I don't see this as realy work, it should go hand in hand with our Python3 porting efforts. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev