-
-
Notifications
You must be signed in to change notification settings - Fork 48
Fix peewee issues with pyright when updating a CharField and then saving it #200
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
Comments
I came across the same issue and checked Peewee’s GitHub — it looks like there’s no existing issue about this. This is question somehow very similar to issue #201 . |
Asking for help upstream is indeed a good idea, please do, thanks. |
Reported to upstream: coleifer/peewee#2980 |
Maybe worth to give a try to https://pypi.org/project/types-peewee/ |
lol This one works. I am testing on it rn. |
I'm not sure why, but this solution seems a bit unstable. I'm currently looking for more type stubs for Peewee, so any suggestions are welcome! :) |
what kind of instability? |
Yeah, I just meant that Pyright was picking up the types-peewee stubs before, (literally after 1 night, but now it’s not lmao. Not sure why rn Update 4/5: Ok. So I double-checked types-peewee. It works as
but isn't
|
I will have a look later, probably not in the coming days however, sorry |
When updating an ORM object (e.g.
book.html_etag = etag
), #191 had to add# type: ignore
hint because pyright was complaining that astr
cannot be used to set aCharField
This is clearly a peewee issue, maybe linked to the fact that we are using an old version.
To be fixed / reported upstream if not already fixed.
The text was updated successfully, but these errors were encountered: