# Document BINARY\_OP\_ opcodes?

**URL:** <https://discuss.python.org/t/document-binary-op-opcodes/23884>\
**Category:** Documentation\
**Created:** [February 14, 2023, 5:58pm UTC](https://discuss.python.org/t/document-binary-op-opcodes/23884 "2023-02-14T17:58:27Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [February 15, 2023, 1:33am UTC](https://discuss.python.org/t/document-binary-op-opcodes/23884/4 "2023-02-15T01:33:35Z")

</div>

> [@smontanaro](#):
>
> That said, there seems to be an error in the `BINARY_OP` documentation, namely the introduction version. That opcode (ignoring the variants you mentioned) has been around for as long as I’ve been messing around with Python (1.0 timeframe).

Actually, what has been around through 3.10 was separate opcodes BINARY\_OP\_ADD, BINARY\_OP\_MULTIPLY, and so on. In 3.11 these were combined into BINARY\_OP, with the oparg indicating which operation to perform. So I think the version mentioned in the docs is correct.

---

_[View the full topic](https://discuss.python.org/t/document-binary-op-opcodes/23884)._
