On Fri, Jul 18, 2014 at 10:34:00AM -0400, Bohuslav Kabrda wrote:
----- Original Message -----
> On Fri, Jul 18, 2014 at 10:22:07AM -0400, Bohuslav Kabrda wrote:
> > ----- Original Message -----
> > > One more question -- why do you see as preferable to select the python
> > > version we are building for? With your patch, the code would run equally
> > > well with /usr/bin/python pointing to python2 and python3, right? So can
> > > we just use whatever /usr/bin/python points to and be happy? Why should
> > > the maintainer select one (or even two) python releases?
> >
> > Because some libraries/applications depending on sssd might not be ported
> > to whichever Python sssd is compiled with. E.g. if you compiled just with
> > python3, people wouldn't be able to import sssd from python2 and vice
> > versa. All major distributions I know build parallel Python 2 and Python 3
> > stacks because of it and they try to have as much built for both Python
> > versions as possible. Imagine you would stop building python2 bindings
> > while half of your fedora dependencies isn't ported to Python 2 :)
>
> Ah, that's a good point, thanks.
>
> In that case, I prefer option 2) above as well and also the suggestion
> to test with both selected python versions makes perfect sense now.
>
> Thanks for the explanation! Now, to proceed with the patch you
> suggested, would you like us to code up the build changes?
I'd highly appreciate if you could do the build changes yourself, I probably
won't be able to get to any coding next week or two and I think it's better to get
this merged and tested sooner than later.
OK:
https://fedorahosted.org/sssd/ticket/2386
Out of curiosity, is there some Fedora Feature or a bug that tracks
converting packages to Python 3? Do we need to hit some particular
deadline?
> > To sum it up, you should be able to choose what Python you're building
> > with, IMO.
> > Also, because of Python upstream recommendation, /usr/bin/python will
> > probably keep pointing to python2, maybe even forever. So it will come
> > down to each Linux distro own policy to say which Python is the "default
> > one" and which is the "optional one".
>
> Right, but on some distributions (ArchLinux comes to mind),
> /usr/bin/python points to python3 already.
Yes, and I think it's Arch only. And they actually were the reason why Python
upstream created this recommendation for other distros - Fedora, for one, is going to
adhere to it, so we'll keep /usr/bin/python pointing to python2 even if we'll
pronounce python3 "the default" Python interpreter.
Thanks for the clarification.