| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | f-strings everywhere | David Lord | 2020-04-19 | 1 | -2/+2 |
| | | |||||
| * | apply pyupgrade --py36-plus | David Lord | 2020-04-19 | 1 | -9/+8 |
| | | |||||
| * | Merge branch '7.x' | David Lord | 2020-03-08 | 1 | -126/+139 |
| |\ | |||||
| | * | apply pyupgrade | David Lord | 2020-03-08 | 1 | -1/+1 |
| | | | |||||
| | * | apply formatting | David Lord | 2020-03-06 | 1 | -5/+1 |
| | | | |||||
| | * | apply flake8 | David Lord | 2020-03-06 | 1 | -23/+16 |
| | | | |||||
| | * | apply black | David Lord | 2020-03-06 | 1 | -94/+115 |
| | | | |||||
| | * | apply reorder-python-imports | David Lord | 2020-03-06 | 1 | -3/+2 |
| | | | |||||
| * | | Merge branch '7.x' | David Lord | 2020-02-19 | 1 | -0/+38 |
| |\ \ | |/ | | | | | | | # Conflicts: # CHANGES.rst | ||||
| | * | type is always IOBase, handle lazy file | David Lord | 2020-02-19 | 1 | -9/+14 |
| | | | |||||
| | * | Formatting file option prompting to path only | icreatedanaccount | 2020-02-19 | 1 | -0/+13 |
| | | | |||||
| | * | Restore progressbar iterator interface; add test | Stephen Rosen | 2020-02-16 | 1 | -0/+20 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add a test for iterating on a progressbar with next() - implement `next()` in terms of `iter(ProgressBar)`, which is already well-defined - add a note about slow operations with progressbar to narrative docs One of the keys to this working is that `ProgressBar.generator` is consuming an iterable and doesn't store any important state in local variables, making it re-entry safe. I wasn't sure how we can best hint in the public docs that simply walking the bar and stopping one step short of finishing will result in the progress bar "hanging" unfinished. Noting that we work well with things like `time.sleep()` seems like a decent way of advertising positively something which we support *and* guiding anyone going off-book into proper usage. closes #1125 | ||||
| * | | allow ProgressBar.update to set current_item | Christopher Palmer | 2019-08-01 | 1 | -0/+44 |
| |/ | | | | | This allows updating what item is displayed when using ProgressBar.update to control the exact progress. | ||||
| * | fix py2 windows getchar test | David Lord | 2019-08-01 | 1 | -1/+3 |
| | | |||||
| * | Expand unit testing around termui (getchar testing for Windows) | icreatedanaccount | 2019-05-24 | 1 | -2/+145 |
| | | |||||
| * | Add missing fake clock in termui tests | Jan Christoph Bischko | 2018-05-15 | 1 | -2/+7 |
| | | |||||
| * | Fix test for delayed progress bar display | Jan Christoph Bischko | 2018-05-15 | 1 | -2/+83 |
| | | |||||
| * | length hint test: ensure iterator compatibility for older python versions | Ronny Pfannschmidt | 2015-12-13 | 1 | -0/+2 |
| | | |||||
| * | introduce int_types compat to fix python3 type error in _length_hint | Ronny Pfannschmidt | 2015-12-13 | 1 | -0/+28 |
| | | |||||
| * | Added termui tests | Armin Ronacher | 2014-08-11 | 1 | -0/+14 |
 |
index : delta/python-packages/click.git | |
| github.com: pallets/click |
| summaryrefslogtreecommitdiff |