which version of tqdm are you using?

tqdm==4.18.0

Edit: I use a high dpi display with 150% scaling, if that matters.

Edit 2: when I set the font size to 14, it works correctly. But I need to set the font size to 16 (because of the high dpi), and with this font, the effect is as I shown above.

interesting. so windows is incorrectly reporting the terminal width when you mess with fonts and scaling. you could always use trange(..., ncols=75) or whatever to fix the width

Setting ncols does not help. The progress bar is shorter but the text still wraps if the number of iterations is sufficiently large. Interestingly, I see the cursor positioned beyond the line (see screenshot) and it moves further with each iteration, eventually skipping to a new line.

Progress bar works fine with ascii=True. There is obviously an error with unicode characters in Windows console.

yes looks like it. I just tried win10 + py27, and couldn't get unicode working at all. it could be that windows thinks the unicode characters are "widechars"

Unicode support for Windows console was added in python 3.6. So it should work for me. Maybe the number of characters going backwards when updating the bar is calculated incorrectly? It's strange that the result depends on the font size. BTW, I believe that Unicode characters are widechars.

well, the true widths of many unicode chars are not wide, which some environments don't seem to understand

I cant confirm the experience above inside the windows comand line. But i have this problems when i use the PyCharm console.

With mutlithreading support, like i already mentioned in #329.

I get this output with unicode:

D:\Iceflower\programming\tqdm>python test.py
#0, est. 2.50s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:05<00:00, 840.30it/s]
#1, est. 1.70s:  99%|███████████████████████████████████████████████████████████? | 4936/5000 [00:05<00:00, 838.44it/s]
#1, est. 1.70s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:05<00:00, 838.20it/s]
#2, est. 1.20s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:05<00:00, 836.62it/s]
#3, est. 1.00s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 833.22it/s]
#4, est. 0.83s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 823.69it/s]
#5, est. 0.71s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 830.42it/s]
#6, est. 0.62s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 821.60it/s]
#7, est. 0.56s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 816.37it/s]
#8, est. 0.50s: 100%|█████████████████████████████████████████████████████████████| 5000/5000 [00:06<00:00, 823.41it/s]
D:\Iceflower\programming\tqdm>

and this with ascii=True

D:\Iceflower\programming\tqdm>python test.py
#0, est. 2.50s: 100%|###########################################| 5000/5000 [00:05<00:00, 853.46it/s]
#1, est. 1.70s:  98%|##########################################2| 4917/5000 [00:05<00:00, 847.49it/s]
#1, est. 1.70s: 100%|###########################################| 5000/5000 [00:05<00:00, 848.74it/s]
#2, est. 1.20s: 100%|###########################################| 5000/5000 [00:05<00:00, 849.17it/s]
#3, est. 1.00s: 100%|###########################################| 5000/5000 [00:05<00:00, 844.14it/s]
#4, est. 0.83s: 100%|###########################################| 5000/5000 [00:05<00:00, 844.86it/s]
#5, est. 0.71s: 100%|###########################################| 5000/5000 [00:05<00:00, 841.36it/s]
#6, est. 0.62s: 100%|###########################################| 5000/5000 [00:05<00:00, 842.14it/s]
#7, est. 0.56s: 100%|###########################################| 5000/5000 [00:05<00:00, 842.64it/s]
#8, est. 0.50s: 100%|###########################################| 5000/5000 [00:05<00:00, 839.17it/s]
D:\Iceflower\programming\tqdm>

Hey guys, thanks for your answers.
I tried with setting ascii = True, then it works well on my windows.

On windows 10 development in PTVS, python dos console output looks as follows with simple range. Notice the odd \uXXXX chars at the end. This also causes status on each newline unless ncols reduced:

for x in tqdm(range(10000)):
        sleep(0.001)

That's partial unicode support. You can probably fix it with tqdm(..., ascii=True)

@IceflowRE your PyCharm issue is mentioned in https://github.com/tqdm/tqdm#faq-and-known-issues

Might add to the FAQs that environments which lie about unicode support will also have problems without ascii=True

ta, yup, tried ascii=True after following an earlier comment thread and it did the trick.

I added ascii=True to the call, but still get the issue.

Environment:

Using git-bash on Windows 10 to connect to an Ubuntu server. Code is run on the Ubuntu server, and the output is viewed from the git-bash console on Windows 10.

I can confirm this issue occurs on a Raspberry Pi when using the defaults. Usually the bar flows as normal, but occasionally on both Windows (terminal emulator for zsh/ubuntu image) and Raspbian Buster it will show a standard replacement character (�) and skip a line. The character may show up in a random location along the progress bar, not at the end.

ascii=True resolves the issue, but I kind of dig the smooth bar when it works. Oddly it works most of the time, it's only once in a while that it happens. Particularly for tracking the download of a larger file. Terminal font shows as Monospace Regular according to LXTerminal in Raspbian Buster, and DejaVu Sans Mono for Powerline in mintty 3.0.0 running terminal emulation for WSL on Win10.

Still persists on Windows 10 terminal for me, also with ascii=True. Python 3.8.0, tqdm version 4.39.0.

Hi,
Currently, I use tqdm in PuTTy in windows 10.
But the putty is connected to a linux server.
The output progress bar is broken.
There are many new lines, like the image below.
Does any have idea to solve it?
Thanks in advance.

below is the locale setting.

The version of tqdm I used is 4.48.2

Hi,
Currently, I use tqdm in PuTTy in windows 10.
But the putty is connected to a linux server.
The output progress bar is broken.
There are many new lines, like the image below.
Does any have idea to solve it?
Thanks in advance.

below is the locale setting.

The version of tqdm I used is 4.48.2

Do not tick this option
It works for me

'ascii=True' still not work for me. But though the code below, the symptoms can be relieved a little.

import time
from tqdm import tqdm

with tqdm(total=3, desc='level_1', position=0, leave=False) as pbar:
    for i in tqdm(range(3)):
        for j in tqdm(range(5), desc='level_2', position=0, leave=True):
            time.sleep(0.1)
        pbar.update()

@MacwinWin sounds like you're missing colorama #1139 which should become automatic next release #1180

@casperdcl Thanks a lot.

# this is my tqdm function
for row in tqdm(file, total=file_line_count(file_path)):

There is still a small question mark/empty rectangle symbol appearing for me in the Windows Command Prompt and Windows Powershell.

This is running on Windows Server 2022 Datacenter 21H2 using Python 3.10.2 and tqdm-4.62.3.

Everytime I restart Terminal multiplexing like tmux or screen,many lines of tqdm will appear on the screen