| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| # The following definition crashes stubtest. | ||
| # def set_encryption( | ||
| # self, | ||
| # owner_password: str, | ||
| # user_password: str | None = None, | ||
| # encryption_method: EncryptionMethod | str = ..., | ||
| # permissions: AccessPermission = ..., | ||
| # encrypt_metadata: bool = False, | ||
| # ) -> None: ... |
There was a problem hiding this comment.
This needs further investigation for which I didn't have time yet.
Sorry, something went wrong.
There was a problem hiding this comment.
I just ran this against stubtest HEAD and this seems to fix it. I'll update the comment.
Sorry, something went wrong.
|
I think we'll need a pytype release that includes google/pytype@829c589 if you want to keep the string default values — or you could take them out for now, and add them back when we have the new pytype release |
Sorry, something went wrong.
|
@rchen152 Is there a timeline for the next pytype release? This is non-critical, since we can easily work around the issue, but if a release is due soon, I would rather wait. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, just a few points
Sorry, something went wrong.
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
|
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
Sorry, something went wrong.
Sorry for the delay! (Yesterday was MLK day here.) We usually aim to do one pytype release a week. It's a manual process, so there's no fixed schedule. Yesterday's nightly tests were clean, so I can cut a release right now, actually. |
Sorry, something went wrong.
That would be great, if possible! It would help unblock #9501 |
Sorry, something went wrong.
|
Done! The new pytype version is 2023.01.17. |
Sorry, something went wrong.
Amazing, thank you! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Closes #9542