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 soft
On 10.8.2016 23:36, Jason L Tibbitts III wrote:
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
absence of version-specific bits. That package builds for an arbitrary
number of system pytho
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% package
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 mean
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 or
> projects with few
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
Hi!
No, this automatic Provides generator does not create "python(name)".
Only "pythonX.Ydist()" and "pythonXdist()".
On 08/10/2016 07:09 PM, Avram Lubkin wrote:
Is an unversioned python(name) also being created automagically? I
manually create these for the command line tools which support
> "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 know I
really should
