Feat: Rewrite File.download into download_to_drive and download_to_object#3223
Feat: Rewrite File.download into download_to_drive and download_to_object#3223Bibo-Joshi merged 27 commits intomasterfrom
Conversation
|
I dont get codecov path, python-telegram-bot/tests/test_file.py Lines 157 to 167 in 27a0fca Edit: Doesn't complain anymore. I think it has seen its error :D |
Bibo-Joshi
left a comment
There was a problem hiding this comment.
Thanks for the PR! I left some comments, some of which are not actually due to your changes :D
IISC Codecov mainly complains about decrypting files with self._credentials not being covered.
Regarding naming, I'd like to also throw download_to_file (as alternative to download_to_drive) and download_to_memory (as alternative to download_to_obj) into the race.
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
Co-authored-by: Harshil <37377066+harshil21@users.noreply.github.com>
|
There are open questions I have now, unordered as I think of them.
|
|
So I finally got around to review this again and I apologize for taking so long.
LGTM.
That would mean tuching passport tests. grrrrrrr. I'm okay with only touching them if absolutely necessary xD
Okay with me, can be a separate PR though.
No clue, goes back to #1168. IISC removing should be fine, maybe in the same PR as the hash param
It does not, actually 🤔 Even for local files, they should be encrypted, I guess. Can you fix that + add tests? |
Also improved docs for the tests
harshil21
left a comment
There was a problem hiding this comment.
nice work, didn't look at the tests too closely:
Bibo-Joshi
left a comment
There was a problem hiding this comment.
Thanks for the updates & the improvements for local encrypted files!
examples/conversationbot.py
Outdated
There was a problem hiding this comment.
This may have to change to (20, 0, 0, "beta", 0) … suggestions for a good place to keep track of that? 😬
There was a problem hiding this comment.
Maybe in the release page? But it's hard to say when a change breaks an example post those changes
There was a problem hiding this comment.
I'm mainly talking about our plans to make the next release a beta release. Only if we get another API update before #3249 is mergable, the next release would be calld 20.0a5 … Mind you, this check would still be correct, since (20, 0, 0, "alpha", 5) < (20, 0, 0, "beta", 0), but it would probably still confuse users xD I'll add a note o the "how to release page" as reminder :)
Also rename to_drive to to_memory
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
Bibo-Joshi
left a comment
There was a problem hiding this comment.
precommit and doc-build are failing 🤔
otherwise LGTM 🙂
TODO after merge: Update wiki and transition guide/script
Checklist for PRs
.. versionadded:: version,.. versionchanged:: versionor.. deprecated:: versionto the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)AUTHORS.rst(optional)__all__s