Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support running gitstats in a python3-only environment #94

Open
xsgordon opened this issue Aug 6, 2019 · 3 comments
Open

Support running gitstats in a python3-only environment #94

xsgordon opened this issue Aug 6, 2019 · 3 comments

Comments

@xsgordon
Copy link
Contributor

xsgordon commented Aug 6, 2019

It's been brought to my attention that Fedora 31 will be going Python3 only:

https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal
https://bugzilla.redhat.com/show_bug.cgi?id=1737997

As it stands this will result in the removal of gitstats from the Fedora repositories, though I am investigating how to avoid this (by e.g. carrying patches to make it python3 compatible).

I thought I'd ask however if there was any plan with regards to supporting python3 for gitstats, as while Fedora is likely pushing the curve here other distributions may follow suit in future? As far as I can tell this last came up back in 2015 as distros started defaulting /usr/bin/python to python3:

#52
https://bugzilla.redhat.com/show_bug.cgi?id=1583357

@sebix
Copy link

sebix commented Aug 9, 2019

@xsgordon
Copy link
Contributor Author

xsgordon commented Aug 9, 2019

Yes, I'm actually aware of repostat. Before I go that route as the package maintainer for gitstats in Fedora I'm checking what the approach of the gitstats project itself is. If in the end the only answer is repostat that's fine but given the change in upstream provenance I likely have to submit it as if it's a new package (or just orphan gitstats and leave someone else to take this up).

@sebix
Copy link

sebix commented Aug 9, 2019

That repo is dead for years and there are lots of duplicate questions/comments in the issues and pull requests.

For the python3 part see #41 so for this problem only you have a solution. But I'd rather go the way to obsolete this one and use the fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants