this post was submitted on 09 Mar 2025
18 points (87.5% liked)

Python

6788 readers
41 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
 

if coin == 25 | 10 | 5:

If I replace the '|' with 'or' the code runs just fine. I'm not sure why I can't use '|' in the same statement.

Doing the following doesn't work either:

if coin == 25 | coin == 10 | coin == 5:

I know bitwise operators can only be used with integers, but other then that is there another difference from logical operators?

you are viewing a single comment's thread
view the rest of the comments
[–] ExtremeDullard@lemmy.sdf.org 48 points 1 day ago* (last edited 1 day ago) (1 children)

Much to unpack here...

coin == 25 | 10 | 5

...will evaluate as True if coin is equal to the bitwise OR of 25, 10 and 5 - i.e. 31. In other word, it's equivalent to coin == 31. That's because the bitwise OR has precedence over the == operator. See operator precedence in Python.

If I replace the ‘|’ with ‘or’ the code runs just fine.

It probably doesn't. If you replace | with or, you have the statement coin == 25 or 10 or 5 which is always True in the if statement because it's evaluated as (coin == 25) or (not 0) or (not 0) in an if statement.

coin == 25 | coin == 10 | coin == 5

...will evaluate as coin == (25 | coin) == (10 | coin) == 5. Again, operator precedence.

What you want to do is this:

if coin in [25, 10, 5]:

or

if coin in (25, 10, 5):

or simply

if coin == 25 or coin == 10 or coin == 5:

Don't create problems and confusion for the next guy who reads your code for nothing. Simple and readable are your friends 🙂

[–] milon@lemm.ee 3 points 1 day ago (3 children)

Thanks. I think I understand why I wouldn't want to use it in this case. But what is an example of where I can use it? This makes me think I should avoid using bitwise operators with integers and keep it to strings only, but I know that's not true from what I've learned.

[–] driving_crooner@lemmy.eco.br 2 points 10 hours ago* (last edited 2 hours ago)

I use that in match case operations, but usually when is just two possibilities, try something like this and see if works

match coin:
case 5 | 10 | 20:
...

Edit: just tested and it's works.

[–] wewbull@feddit.uk 8 points 1 day ago* (last edited 1 day ago) (1 children)

When you're working with the binary representation of numbers.

In your code you had three numbers 25, 10 and 5. If we write those number in binary we get:

  • 25: 0b00011001
  • 10: 0b00001010
  • 5: 0b00000101

(The 0b at the start is just a way of saying "this is binary")

When you do a bitwise-or, it's a bit like adding up but you don't bother with carrying anything. So let's do 25 | 10, starting at the right-hand end going bit by bit (bitwise):

  • 0 | 1 = 1
  • 1 | 0 = 1
  • 0 | 0 = 0
  • 1 | 1 = 1
  • 1 | 0 = 1
  • 0 | 0 = 0 for all the rest

So the result is 0b00011011 which is 27.

So now you're asking "when would I ever need to do such a thing?" and the flippant answer is "you'll know when you need it".

You're looking for more though, I know. Basically computers often put multiple bits of data into bitstreams (long sequences of bits). Think networking and file storage. Constructing these bitstreams is done with bitwise operators like |, &, ^, << and >>. Together they form a different type of maths to what you're used to.

These operators work in a very similar way to how +, -, * and / work. They take two numbers and return a third. If we rewrite your code using operators you're more familiar with...

    if coin == 25 | 10 | 5:  # if coin == 31
        ...
    if coin == 25 + 10 + 5:  # if coin == 40
        ...

...you can see it's obviously wrong because you're doing one comparison with the result of the operation (addition or bitwise-or), not three comparisons.

[–] milon@lemm.ee 3 points 12 hours ago

Thank you for the thorough explanation. It makes sense to me why I had the error that I did. I'll keep this in mind next time when I consider using a bitwise operator.

[–] ExtremeDullard@lemmy.sdf.org 10 points 1 day ago* (last edited 1 day ago) (1 children)

But what is an example of where I can use it?

Aside from operations on bitfields, a bitwise operator can be useful in several "non bits" cases. For instance:

value & 1 evaluates to 1 if value is odd (and will evaluate to True in an if statement)
value >> 1 divides value by 2 (integer division)

But usually bitwise operators are for when you want to manipulate bits in values. For instance:

value | 5 returns value with bits 1 and 3 set to True
value & 0xffff returns the 16 least-significant bits in value (usually you do this to make sure it will fit in 2 bytes in memory for example)
value & (0xffff ^ 5) returns the lower 16 bits of value with bits 1 and 3 set to False

Etc.

[–] milon@lemm.ee 5 points 1 day ago (3 children)

Thank you for the reply. It seems bitwise operators are somewhat of an advanced concept that I may revisit down the road.

[–] pupbiru@aussie.zone 1 points 3 hours ago* (last edited 3 hours ago)

python in general tends toward readability over performance optimisation… you’re right they’re an advanced concept, and i’d say if you ever use bitwise operators in python they should be wrapped in some descriptive and very minimal function: treat it like a black box, because the next person that comes along likely won’t understand what’s happening without a pretty good description

a bit field is just not a descriptive data structure, so manipulate it directly as little as possible

i’d also say that most peoples use of bitwise operators is when unpacking external data formats (network traffic, operating system primitives, files formats, etc) and they’re usually wrapped in data structures that make those things more pythonic

unless you know you need bitwise operators, you probably don’t need bitwise operators

[–] iltg@sh.itjust.works 9 points 1 day ago (1 children)

honestly yes you're probably not going to use them a lot, if at all, especially in python

You might use them with sets:

a = {1, 2, 3}
b = {2, 3, 4}

a | b  # {1, 2, 3, 4}
a & b  # {2, 3}
a ^ b  # {1, 4}
a - b  # {1}
b - a  # {4}
[–] ExtremeDullard@lemmy.sdf.org 2 points 1 day ago (1 children)

They're quite simple. Just convert the values to binary and apply the applicable truth tables. Just remember operator precedence when you use them, and in doubt, don't trust your luck and apply parentheses generously 🙂

And write generous unit tests so the next person doesn't accidentally mess it up.