Moving to progressbar2 #2

Open
opened 2018-04-21 21:33:08 +02:00 by petronny · 2 comments

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?

BTW, just say Hi :)

As far as I remember, gcp is using the [old progress bar library](https://github.com/niltonvolpato/python-progressbar), which lacks maintenance in Python 3. I prefer the new progressbar library [progressbar2](https://github.com/WoLpH/python-progressbar) which is well maintained and supports both Python 2 and Python 3. Can gcp move to progressbar2? > BTW, just say Hi :)
mcy added the
enhancement
label 2018-05-04 20:30:30 +02:00
Owner

I guess that's a good idea. I'll look into it, thanks! (And hi :-)

I guess that's a good idea. I'll look into it, thanks! (And hi :-)
Owner

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.

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.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mcy/gcp#2
No description provided.