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
[BUG] from rich.progress import read
should be removed from the docs and updated with rich.progress.open
example
#2204
Comments
I had mentioned this being an issue in #1759. I think it's |
from rich.progress import read
doesn't workfrom rich.progress import read
should be removed from the docs
Ah thx, in this case this part should be removed from the docs. Let me try to create an PR for this. |
The docs are still mentioning `rich.progress.read` but the new way is `rich.progress.open` I move the docs handling files to top. I you think progress for reading a file is not basic usage please decline this PR. To have a progress when reading a file is very useful for me, and I personally think this it is a great selling point.
@hwmrocker, not removed but maybe updated to reflect the API change. But I see the changes to reflect that. |
from rich.progress import read
should be removed from the docsfrom rich.progress import read
should be removed from the docs and updated with rich.progress.open
example
The section describing read was a remanent of an older edit. The "Reading from a file" section describes the correct API in more detail. Docs have been updated. |
Did I solve your problem? Why not buy the devs a coffee to say thanks? |
You may find a solution to your problem in the docs or issues.
Describe the bug
When I try to use the new promoted progress for file like objects, as described here
When executing I get this error:
Platform
Click to expand
What platform (Win/Linux/Mac) are you running on? What terminal software are you using?
I may ask you to copy and paste the output of the following commands. It may save some time if you do it now.
If you're using Rich in a terminal:
The text was updated successfully, but these errors were encountered: