On Mon, 28 Oct 2013 09:17, Sascha Peilicke <speilicke@...> wrote:
On Thursday 24 October 2013 15:07:49 Adam Spiers wrote:
Sascha Peilicke (speilicke@suse.com) wrote:
On Saturday 12 October 2013 14:19:57 you wrote:
Hi Sascha !
Is there any possibility we (all python maintainers) discuss our goals both python2 and python3 ?
sure, since Juergen joined recently too, I CC'ed everyone. I dunno how you guys prefer it, we could have an IRC meeting at some point but I guess it's easier to stay with mails just now. Therefore I added opensuse-packaging@ because that's really where we should discuss things.
We receive requests sometimes update and/or new packages which are Python3 compatible.
[snip]
In the long run, py3k will gradually replace py2k in openSUSE, that means if the critical mass is reached and most upstreams moved on, py2k pkgs will slowly fade from Factory. Meanwhile, some pkg upstreams already stopped caring for py2k, so their pkgs simply stay with the last working version. Currently it's more manual work, I agree.
Just saw this interesting data-point - Fedora is going to switch to Python 3 by default:
Jupp. I guess it's more obvious for Fedora than us since they always want to be bleeding edge. But what does that mean in reality? They're not likely going to ditch py2 any time soon. there's just far too much software out there that needs it. Since RH did a wise choice in standardizing on Python for most of their tooling, I'd bet they would have to port a whole lot of stuff first. So in the end it boils down to what /usr/bin/python points too. On openSUSE, it's the same as /usr/bin/python-2.7. I thought about changing this and we discussed this in length. Finally, we decided against it [0]. Others than that, py3k is in very good shape inside 13.1 and will get more packages during the next dev cycle.
[0] http://lists.opensuse.org/opensuse-packaging/2013-08/msg00089.html
IMHO, we need the first step: separate - the (very) Good (python ver does not matter) - the nice (need either py2 or py3 and be honest about) - the bad (work only with one special python version) - the ugly (need either py2 or py3 and tell not, or lie about) The Good is what we want to prefere, they can point to /usr/bin/python . The nice need to point to either /usr/bin/python2 or /usr/bin/python3 . The bad will have to point to a more specific version, e.g. /usr/bin/python2.7 and need to have a special cared for spec file. Goal would be to get them to the nice point. The ugly, well they will need work, no matter what. The more cleanly defined the needs of a package are the easier it will be to handle it in the long run. We will need a time with a (peacefull) coexistence of python 2 and 3 . Having the programs point to either python2 or python3 is a step in the right direction, and helps to keep the hassle down. Some packages (e.g. calibre) will need special care, no matter what. Our goal should be raising sensitivity upstream. Having them in the know and care about this lowers the problem for all distros. The trouble will be getting some of upstream to care about this. Thats my 2ct on this. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org