Re: Automatic Provides: Discussion summary and plan

> "TO" == Tomas Orsava writes: TO> That looks incredible! Why didn't it see the light of day? Time TO> constraints or some technical issues? Well, it sort of fell by the wayside as I got involved with other things. I've learned a lot about RPM internals since then and I

Re: Automatic Provides: Discussion summary and plan

Yeah, I really wish I had actually pushed through the macro work I had done last year. You can see that at https://pagure.io/python-macros A spec would look like this: https://pagure.io/python-macros/blob/master/f/test1.spec And most of that is actually implemented. Note the almost complete

Re: Python 3 porting: 50% done in Rawhide 

On Thu, Aug 11, 2016 at 6:48 AM, Petr Viktorin wrote: > > Instead, we should shift our focus from porting specfiles to upstream > projects. At this point, if some software is easy to port it was probably > ported already; what we're left with are either tough nuts to crack

Re: Python 3 porting: 50% done in Rawhide 

On 08/11/2016 09:48 AM, Petr Viktorin wrote: Hello, As of now, http://fedora.portingdb.xyz shows that we are 50% done porting Fedora packages to Python 3. This is a big magic milestone; if you're looking for a reason to celebrate, this is it! :) Meanwhile, let me talk about what the number

Python 3 porting: 50% done in Rawhide 

Hello, As of now, http://fedora.portingdb.xyz shows that we are 50% done porting Fedora packages to Python 3. This is a big magic milestone; if you're looking for a reason to celebrate, this is it! :) Meanwhile, let me talk about what the number means and what the next steps are. 50%

Python 3.5 for Fedora 23

Hi, As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions). Those builds will be installable alongside regular python3/python packages and will be normal packages, no