Skip to content

Commit 1b4d483

Browse files
committed
Merge branch 'monoSpace'
2 parents 58faf79 + d8d2a66 commit 1b4d483

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,7 @@ iterable with "tqdm(iterable)", and you're done!
2323
2424
Here's what the output looks like:
2525

26-
76%\|████████████████████\             \| 7641/10000 [00:34<00:10,
27-
222.22 it/s]
26+
``76%|████████████████████████████         | 7568/10000 [00:33<00:10, 229.00it/s]``
2827

2928
``trange(N)`` can be also used as a convenient shortcut for
3029
``tqdm(xrange(N))``.
@@ -708,7 +707,7 @@ precompute this by ourselves:
708707
``process_content_with_progress2()`` is better than the naive approach because
709708
now we have predictive information:
710709

711-
50%|████████████\             \| 2/4 [00:00<00:00, 4.06it/s]
710+
``50%|████████████            | 2/4 [00:00<00:00, 4.06it/s]``
712711

713712
However, the progress is not smooth: it increments in steps, 1 step being
714713
1 file processed. The problem is that we do not just walk through files tree,
@@ -750,7 +749,8 @@ Below we implement this approach using a manually updated ``tqdm`` bar, where
750749
And here is the result: a much smoother progress bar with meaningful
751750
predicted time and statistics:
752751

753-
47%|████████████\             \| 152K/321K [00:03<00:03, 46.2KB/s]
752+
``47%|████████████             | 152K/321K [00:03<00:03, 46.2KB/s]``
753+
754754

755755

756756
Contributions

0 commit comments

Comments
 (0)