Moving to progressbar2 #2
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mcy/gcp#2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As far as I remember, gcp is using the old progress bar library, which lacks maintenance in Python 3.
I prefer the new progressbar library progressbar2 which is well maintained and supports both Python 2 and Python 3.
Can gcp move to progressbar2?
I guess that's a good idea. I'll look into it, thanks! (And hi :-)
A new version of the original progressbar was released in June, with better Python3 support (it seems):
https://pypi.org/project/progressbar/#history
There is also a case in Debian to possibly switch to progressbar2, and I would like for it to be resolved before deciding to switch, since using progressbar2 would most likely break gcp in Debian (and possibly other distros):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839149
That being said, as I wrote in reply to this Debian bug report, progressbar2 inspires more confidence and switching would still probably be a good idea.