this post was submitted on 16 Mar 2026
16 points (100.0% liked)

Python

7811 readers
33 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 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
16
PEP: Is initializing typed variable with None bad practice? (lemmy.world)
submitted 12 hours ago by AstroLightz@lemmy.world to c/python@programming.dev
9 comments fedilink hide all child comments
 

For example:

class FooBar:
    def __init__(self):
        self.a: int = None
        self.foo: str = None

Is this bad practice/go against PEP guidelines or is it fine?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] solrize@lemmy.ml 2 points 4 hours ago* (last edited 4 hours ago) (1 children)

I'm going to say initializing them to None and updating them later is a code smell. If you can do so, make them non-optional and always initialize them to actual meaningful values.

[โ€“] jtrek@startrek.website 1 points 59 minutes ago

Yeah, if you initialize them to None then for the entire rest of the class you're going to have to account for the possibility that they're None. If it's unavoidable that they might be None, you should type it as such.

If you type them as like str | None then later when you do like return foo[0] it will warn you that you can't do that with None.