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

tqdm.write() does not work well with process_map() #1081

Open
5 of 8 tasks
nikhilweee opened this issue Nov 24, 2020 · 1 comment
Open
5 of 8 tasks

tqdm.write() does not work well with process_map() #1081

nikhilweee opened this issue Nov 24, 2020 · 1 comment

Comments

@nikhilweee
Copy link

nikhilweee commented Nov 24, 2020

Checklist

  • I have marked all applicable categories:
    • exception-raising bug
    • visual output bug
    • documentation request (i.e. "X is missing from the documentation." If instead I want to ask "how to use X?" I understand StackOverflow#tqdm is more appropriate)
    • new feature request
  • I have visited the source website, and in particular
    read the known issues
  • I have searched through the issue tracker for duplicates
  • I have mentioned version numbers, operating system and
    environment, where applicable:
    >>> import tqdm, sys
    >>> print(tqdm.__version__, sys.version, sys.platform)
    4.47.0 3.8.3 (default, Jul  2 2020, 16:21:59) 
    [GCC 7.3.0] linux

Issue

Normally when I want to display text along with a running progress bar, I would use tqdm.write() instead of print() and it all works well. However, when I use process_map(), tqdm.write() interrupts the progress bar, just like print(). It would be great if tqdm.write() works with process_map() as well.

@nikhilweee nikhilweee changed the title tqdm.write() does not work well with process_map tqdm.write() does not work well with process_map() Nov 24, 2020
@nikhilweee
Copy link
Author

I guess this would be another list item in #737

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

1 participant