21
Has using 'thing = liststr <>' instead of 'thing: list[str] = []' any downsides? (feddit.de)
submitted 1 year ago* (last edited 1 year ago) by wasabi@feddit.de to c/python@programming.dev
12 comments fedilink hide all child comments

I have seen some people prefer to create a list of strings by using thing = list[str]() instead of thing: list[str] = []. I think it looks kinda weird, but maybe that's just because I have never seen that syntax before. Does that have any downsides?

It is also possible to use this for dicts: thing = dict[str, SomeClass](). Looks equally weird to me. Is that widely used? Would you use it? Would you point it out in a code review?

you are viewing a single comment's thread
view the rest of the comments
[-] amanaftermidnight@lemmy.world 12 points 1 year ago

You'd always want to use varname: type_description = initial_value pattern. It's readable, is the same pattern you use in method params, and linters and IDEs recognize this pattern. And it makes sense for the type description be on the left side of the assignment operator, together with the variable it's describing.

[-] qwop@programming.dev 1 points 1 year ago

I'm pretty sure most type checkers recognise both forms.

this post was submitted on 12 Sep 2023
21 points (100.0% liked)

Python

6412 readers
4 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
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev