this post was submitted on 06 Jul 2023
8 points (100.0% liked)

Python

6317 readers
13 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
8
When to use typing.TYPE_CHECKING (feddit.de)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
13 comments fedilink hide all child comments
 

After learning about TYPE_CHECKING i made it a habit to put all imports that were only needed for type checking into an if TYPE_CHECKING: guard. But now I am wondering if that is actually intended to be used like that. Checking whether an import is only needed at type checking time can get quite tedious and sometimes you run into situations were you introduced some code that made the import a requirement at runtime.

How do you use TYPE_CHECKING? Whenever it is possible or only when using it actually solves a circular import?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] rusty 2 points 1 year ago* (last edited 1 year ago)

That's a very cool feature, had no clue about it!

If it doesn't have any visible downsides, it's be nice use it whenever possible. This should provide the additional benefit of having the imports clearly separated.

The tediousness aspect of it makes me wonder though. I'd probably just only use it when I'm specifically importing something only for typing .

Maybe could be a cool feature request for an lsp as well.