)
--
Craig
From adbefcd104e9f6bfb16ffc4aed60cf57295f2c1c Mon Sep 17 00:00:00 2001
From: Craig Rodrigues
Date: Sat, 14 Nov 2015 16:43:44 -0800
Subject: [PATCH 1/4] Use print() as a function for Python 3. [PEP 3105]
import __future__.print_function to keep things working on Python 2.
---
.../libhugetlbfs
Hi,
The upstream for this project is not on github. I just used github as
a temporary place to do my work and display my patches.
The upstream for this project is
https://git.fedorahosted.org/git/kernel-tests.git
I'm not sure who are actively committing to that repo, other than the
people in th
Hi,
The upstream maintainer took my changes at
https://git.fedorahosted.org/git/kernel-tests.git
Thanks.
--
Craig
On Sat, Dec 19, 2015 at 10:24 AM, Craig Rodrigues
wrote:
>
> I filed this bug to track things:
> https://bugzilla.redhat.com/show_bug.cgi?i
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
This is not directly related to Fedora, but I thought people on this list
might be interested in how the transition to Python 3.5 as default
happened at Facebook:
http://pyohio.org/schedule/presentation/212/
https://www.youtube.com/watch?v=nRtp9NgtXiA
--
Craig
___
On Thursday, February 2, 2017, Tadej Janež wrote:
>
>
> Which in turn means 'pip3 install Django' actually used the system-wide
> pip3 command which tried to install Django to the system-wide location
> and failed.
>
>
After you create your Python 3 virtualev, what files are in the bin
directory o
In the Python 3 porting FAD in 2015:
https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015
This database and web interface was used to keep track of upstream projects
and their Python 3 status:
http://fedora.portingdb.xyz/
Is that database no longer being used?
--
Craig
On Wed, Sep 13, 2017
