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
LACE-626 | Try to run tests using Python 3.9 #11
Conversation
|
@macbre by default we check python 3.9, but we don't require it to pass yet. We just check it to be sure if we are ready to switch to 3.9. But if we want to use 3.9 in Chronos we need pythink-toolbox to pass 3.9 checks also. |
Co-authored-by: Milosz Bednarzak <33376065+miloszbednarzak@users.noreply.github.com>
The latest Pylint 2.6.0 still does not support Python 3.9 -> pylint-dev/pylint@2a86092 is still in master. The question is - do we want to wait for Pylint with Python 3.9 to be released or do we simply ignore pylint warnings in Python 3.9 build for now and tag a new version of |
@macbre I'd rather wait than ignore pylint. Pylint is our guardian angel, so I want to bet on it. |
Waiting for Python 3.9-compatible pylint
Pull request was converted to draft
https://github.com/PyCQA/pylint/milestone/24 - pylint's 2.6.1 milestone is only 41% complete now. We have to wait... |
|
See https://github.com/bethinkpl/chronos/pull/119