this post was submitted on 31 Oct 2024
49 points (96.2% liked)
Python
6421 readers
37 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
๐ Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django ๐ฌ)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
๐ Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
๐ Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
โจ Python Ecosystem:
๐ Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- Pythรถrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think what I'm most confused about is I cannot for the life of me seem to wrap my head around the difference between "assignment" and "equality". They seem exactly the same to me: when a variable is assigned a value, it's equal to that value now.
Even if I were write the program
it would still print
40
. Because x is equal to 20. Because it was assigned the value of 20.Hell, I've even heard Dr. Severance say "equal to" in this context in earlier videos multiple times.
Yeah it's confusing because in maths they are the same and use the same symbol but they are 100% not the same in programming, yet they confusingly used the same symbol. In fact they even used the mathematical equality symbol (
=
) for the thing that is least like equality (i.e. assignment).To be fair not all languages made that mistake. There are a fair few where assignment is like
Or
which is probably the most logical option because it really conveys the "store 20 in x" meaning.
Anyway on to your actual question... They definitely aren't the same in programming. Probably the simplest way to think of it is that assignment is a command: make these things equal! and equality is a question: are these things equal?
So for example equality will never mutate it's arguments.
x == y
will never changex
ory
because you're just asking "are they equal?". The value of that equality expression is a bool (true or false) so you can do something like:x == y
asks if they are equal and becomes a bool with the answer, and then the = stores that answer insidea
.In contrast
=
always mutates something. You can do this:And it will print 4. If you do this:
It will (if the language doesn't complain at you for this mistake) print 3 because the == doesn't actually change
a
.Ohhhhh! I think I get it now!
So
==
means "equals" and is a declaration of the state of things, while=
means "assigned the value of` and is a command toward a certain state of things. A description vs an action. An observation of a thing as opposed to effecting that thing.Is that about right?
Well == is a question or a query rather than a declaration of the state of things because it isn't necessarily true.
You can write
which is perfectly valid code; it will just set
a
to befalse
, because the answer to the question "does 3 equal 4?" is no.I think you've got it anyway.