this post was submitted on 05 Jan 2024
11 points (82.4% liked)

Python

6368 readers
15 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
11
Don't use Python's property (www.b-list.org)
submitted 10 months ago by jnovinger@programming.dev to c/python@programming.dev
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] souperk@reddthat.com 10 points 10 months ago (1 children)

this is a method, and always was a method, I just wanted it to look like an attribute for aesthetic reasons

I think "aesthetic reasons" is an oversimplification. There are certain assumptions a developer makes when reading some code that uses properties. While these assumptions are not clearly defined and may differ per developer, I think there is a common core.

(1) There are no side-effects. The object is not mutated (or any other object), no IO takes place.

(2) The time and space complexity is O(1).

(3) The result is consistent. Consequent calls to the property should return the same value unless there is a mutation between them.

[โ€“] VitulusAureus@lemmy.world 5 points 10 months ago

The combination of properties 1 and 3 makes it a pure function, which is also useful in compiled or jittable languages because it allows for a variety of optimizations.