You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try and run pylint on this, it will crash with an error that "Const is not iterable". (See: pylint-dev/pylint#5935)
Even if pylint fixes the error, we are pinned to pylint 2.5.2 and this still happens there.
This does not affect our SDKs much because most of these enums live in the _generated folder, which is skipped by our pylint rcfile. However, if someone follows our generated code and creates a manual enum, they will observe this behavior. Since we no longer support Python 2, we should start generating these enums with the Python 3 syntax, which is pylint-compatible:
If you try and run pylint on this, it will crash with an error that "Const is not iterable". (See: pylint-dev/pylint#5935)
Even if pylint fixes the error, we are pinned to pylint 2.5.2 and this still happens there.
This does not affect our SDKs much because most of these enums live in the
_generated
folder, which is skipped by our pylintrcfile
. However, if someone follows our generated code and creates a manual enum, they will observe this behavior. Since we no longer support Python 2, we should start generating these enums with the Python 3 syntax, which is pylint-compatible:cc/ @lmazuel @l0lawrence @kashifkhan
The text was updated successfully, but these errors were encountered: