138
OpenAI Demo'd Fixing Issue #2472 Live. It's Still Open Months Later.
(blog.tymscar.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Nov 2025
138 points (100.0% liked)
Programming
23886 readers
370 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Actually the function definition is unchanged. The line that was "added" at the bottom was also "removed" at the top. This is just the Git diff generator being confused, which won't come as a surprise to anyone that has ever used it.
The indendentation really is messed-up though.
An indentation change is a definition code change. And as I pointed out, it's a py file, and Python is an indent-significant language.
Of course, but you said:
It is weird to split the two in your sentence, as only the indentation of the next function definition was changed, not the definition itself.
You can just take the L and say you didn't see that the function definition that was "added" was just "removed" at the top. It is an easy mistake to make, I know I've done it many times.
That's not what happened though.
Changing the indent of the def changes the definition. That's my whole argument.
I don't get why you say "of course", agreeing with my point, but then "it was only the indentation that was changed".