-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
8569 drop py36 support #9116
8569 drop py36 support #9116
Conversation
Seems the newer version of sanic does not have type information yet. I reverted back to 20.3.0 and the type errors are gone again |
3fc6265
to
75a2f3c
Compare
@m-vdb The python 3.6 drop is working for now without the sanic update It seems the last missing puzzle piece is removing the python 3.6 checks from the branch rules of the repository otherwise they are stuck in I don’t know if there’s anything we should take into consideration there as it will disable this check repository wide. I assume the risk is low overall, since we’ll keep all the other 3.7 and 3.8 checks in place - and even if 3.6 would fail that wouldn't matter anymore really |
we can do that for |
ah good to know! I can't do it, since I don't have the necessary edit rights - so up to you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @twerkmeister ! Can you also address the following comments in the code:
- rasa.telemetry
- rasa.utils.common
- tests/test_telemetry.py (and also below in the same file)
(I found those by searching for 3.6
everywhere)
pyproject.toml
Outdated
@@ -93,7 +93,7 @@ pytz = ">=2019.1,<2022.0" | |||
rasa-sdk = "^2.8.0" | |||
colorclass = "~2.2" | |||
terminaltables = "~3.1.0" | |||
sanic = ">=19.12.2,<21.0.0" | |||
sanic = "20.3.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we keep the range though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thing was just when I used poetry update
it changed to 20.13.0 or so and then we had a ton of mypy errors - I think there was some problem with the stubs. I could have a look to see if I can actually resolve that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so maybe >=19.12.2,<20.13.0
? and maybe open a follow-up issue to upgrade sanic and do this investigation there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had to use >=19.12.2,<20.12.0
to not get mypy issues
Co-authored-by: Maxime Vdb <[email protected]>
good catch! Will do! |
Could we please make this a priority? 🙌🏻 We actually need that for the "engine" part of the architecture revamp. We can hack it for now but it's not ideal. |
Hey @tmbo, would you still know from your comment a year ago what can be done here when we drop py3.6? It's not clear whether some functionality was missing in python 3.6 that forces that function to be a generator or whether those generators can be handled differently with py 3.7 onwards? Any pointer would help! Lines 680 to 749 in 3ac9530
Edit: created follow up issue as this is a nice to have for now and the py 36 drop is needed for the engine part of the architecture revamp: #9212 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
wuhuu! 🚀 |
Proposed changes:
Status (please check what you already did):