Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

No progress bar in populate_dp.py #34

Closed
1 task
shivanshuraj1333 opened this issue Mar 10, 2019 · 5 comments · May be fixed by #35
Closed
1 task

No progress bar in populate_dp.py #34

shivanshuraj1333 opened this issue Mar 10, 2019 · 5 comments · May be fixed by #35

Comments

@shivanshuraj1333
Copy link
Contributor

On running populate_dp.py to populate database no progress is shown in console, which is very inconvenient to monitor progress as this process takes appreciable amount of time to complete.

Screenshot from 2019-03-10 11-43-52

  • Add progress bar (like the one shown in the gif) in populate_db.py

This improvement will help developer not user

Screencast2019031012_05_15

@gopuvenkat
Copy link
Collaborator

gopuvenkat commented Mar 10, 2019

This would be useful for a developer (while seeding the database). Are you planning on using pyprind.ProgBar?

@shivanshuraj1333
Copy link
Contributor Author

shivanshuraj1333 commented Mar 10, 2019

No, I was tinkering with tqdm. Both seem fine.

@JayeshShukla
Copy link

@zvr Hi,
I am Jayesh Shukla from Chennai, India. I would love to work with GFOSS in GSOC 19 as it excites me the most.Would be really great if you guide me how get started and start contributing now onwards. Also I would like to work on the this clio project as it drags my attention the most.I would also appreciate @gopuvenkat's help if u can. Thanks a lot guys!!!

@gopuvenkat
Copy link
Collaborator

Hi @JayeshShukla,
Clio is built on Flask framework (language - Python3). Please follow the installation guide provided here to setup the local development environment (along with the required LDAP configuration).
When contributing to this repository, please first discuss the change you wish to make via the Issues page or through Zulip chat.

shivanshuraj1333 added a commit to shivanshuraj1333/clio that referenced this issue Mar 12, 2019
@zvr
Copy link
Collaborator

zvr commented Mar 12, 2019

As it was stated above, this will only help the developer, so it should be done in the lowest priority.
And we should be very careful about adding even more dependencies, especially since they do not help the users.
If this was really needed, it could of course be implemented without adding anything by print.

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

Successfully merging a pull request may close this issue.

4 participants