Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Brian Stinson
On Mar 02 06:53, Bohuslav Kabrda wrote: > - Original Message - ...SNIP... > > I think applications should use /usr/bin/python3.4 (at least packaged > applications). Otherwise we could theoretically end up in a situation where > /usr/bin/python3 is owned by python35, but the application R

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Orion Poplawski
On 03/02/2015 04:53 AM, Bohuslav Kabrda wrote: - Original Message - This is a followup to the EPEL IRC meeting discussion about python 3. I had a couple questions which led me to take Slavek's excellent work and try some changes here: https://fedoraproject.org/wiki/User:Orion/EPEL7_Pyth

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Orion Poplawski
On 03/02/2015 05:11 AM, Dan Callaghan wrote: Is there any reason why we shouldn't just upgrade applications to the python35-* stack straight away, by providing python3-*? The main issue here is that EPEL doesn't have releases, so there is no way to take time to build everything and then push

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Dan Callaghan
Excerpts from Bohuslav Kabrda's message of 2015-03-02 22:17 +10:00: > - Original Message - > > Excerpts from Bohuslav Kabrda's message of 2015-03-02 21:59 +10:00: > > > - Original Message - > > > > Under the current proposal every package with Python 3 dependencies > > > > would hav

Re: [EPEL-devel] distribution component in bugzilla

2015-03-02 Thread Kevin Fenzi
On Fri, 27 Feb 2015 19:15:46 -0700 Orion Poplawski wrote: > Could we get a Distribution component for Fedora EPEL in Bugzilla? > Might be useful for things like > https://bugzilla.redhat.com/show_bug.cgi?id=1197264 Well, we could make such a thing, but not sure it's really suited to these kind

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Kevin Fenzi
On Mon, 2 Mar 2015 06:59:29 -0500 (EST) Bohuslav Kabrda wrote: > - Original Message - > > Excerpts from Orion Poplawski's message of 2015-02-28 04:36 +10:00: > > > all python34 packages are retired > > > > Except there is no way to retire an individual subpackage, is there? >

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Bohuslav Kabrda
- Original Message - > Excerpts from Bohuslav Kabrda's message of 2015-03-02 21:59 +10:00: > > - Original Message - > > > Under the current proposal every package with Python 3 dependencies > > > would have to depend on a specific python3x-* package, so then it would > > > be up to

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Dan Callaghan
Excerpts from Bohuslav Kabrda's message of 2015-03-02 21:59 +10:00: > - Original Message - > > Under the current proposal every package with Python 3 dependencies > > would have to depend on a specific python3x-* package, so then it would > > be up to the maintainers of all those packages t

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Bohuslav Kabrda
- Original Message - > Excerpts from Orion Poplawski's message of 2015-02-28 04:36 +10:00: > > all python34 packages are retired > > Except there is no way to retire an individual subpackage, is there? > Instead we are saying, the python34-* subpackage will just go away. Yeah,

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Bohuslav Kabrda
- Original Message - > This is a followup to the EPEL IRC meeting discussion about python 3. I had > a > couple questions which led me to take Slavek's excellent work and try some > changes here: https://fedoraproject.org/wiki/User:Orion/EPEL7_Python3 > > Main ideas: > - (bikeshedding) -