Re: [EPEL-devel] Python 3 discussion

2015-03-04 Thread Bohuslav Kabrda
- Original Message - On 03/03/2015 06:31 AM, Bohuslav Kabrda wrote: Today, I've made some changes to the proposal to accomodate comments from the previous meeting and from discussion on this list. The diff is here:

Re: [EPEL-devel] Python 3 discussion

2015-03-04 Thread Bohuslav Kabrda
- Original Message - On 03/03/2015 08:35 AM, Kevin Fenzi wrote: On Tue, 3 Mar 2015 07:46:00 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com wrote: ^ Is this step part of a coordinated mass-rebuild, or is this just a period of time after we make the announcement: Hey Packagers:

Re: [EPEL-devel] Python 3 discussion

2015-03-03 Thread Bohuslav Kabrda
- Original Message - 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

Re: [EPEL-devel] Python 3 discussion

2015-03-03 Thread Kevin Fenzi
On Tue, 3 Mar 2015 07:46:00 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com wrote: ^ Is this step part of a coordinated mass-rebuild, or is this just a period of time after we make the announcement: Hey Packagers: be sure to rebuild for python35? That's a good question. I guess we should

Re: [EPEL-devel] Python 3 discussion

2015-03-03 Thread Kevin Fenzi
On Tue, 3 Mar 2015 08:31:20 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com wrote: Today, I've made some changes to the proposal to accomodate comments from the previous meeting and from discussion on this list. The diff is here:

Re: [EPEL-devel] Python 3 discussion

2015-03-03 Thread Orion Poplawski
On 03/03/2015 06:31 AM, Bohuslav Kabrda wrote: Today, I've made some changes to the proposal to accomodate comments from the previous meeting and from discussion on this list. The diff is here: https://fedoraproject.org/w/index.php?title=User%3ABkabrda%2FEPEL7_Python3diff=405180oldid=404782

Re: [EPEL-devel] Python 3 discussion

2015-03-03 Thread Bohuslav Kabrda
- Original Message - snip * applications will need to be rebuilt to pick up a change from python34-* to python35-* which is a bit unfortunate. Is there any reason why we shouldn't just upgrade applications to the python35-* stack straight away, by providing python3-*?

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

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 have to depend

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:

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 to

Re: [EPEL-devel] Python 3 discussion

2015-03-02 Thread Kevin Fenzi
On Mon, 2 Mar 2015 06:59:29 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com 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

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) - I

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 the

Re: [EPEL-devel] Python 3 discussion

2015-03-01 Thread Dan Callaghan
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. What I still don't understand is what this

[EPEL-devel] Python 3 discussion

2015-02-27 Thread Orion Poplawski
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) - I didn't like the wording other, so I went