Open nickdrozd opened 4 days ago
However, it does impose a greater workload on developers and us maintainer. If we change something, we constantly need to make sure to double check all imports or run the risk of something failing.
I don't understand what you mean. There is the minor one-time cost of reviewing this PR (and the other one). What other workload is there?
https://github.com/pylint-dev/pylint/issues/8893 presents a problem for this kind of change.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 95.76%. Comparing base (
88e4bc6
) to head (8d455ab
). Report is 1 commits behind head on main.
🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉
This comment was generated for commit 8d455abd0617a2666560bf3ed0c062cacc9654d4
Type of Changes
Description
Putting https://github.com/pylint-dev/pylint/pull/9964 to the test. Move typechecking imports behind
TYPE_CHECKING
. Also move a few type aliases. The idea is to move out anything that isn't used at runtime.Similar to https://github.com/pylint-dev/astroid/pull/2585