[issue33390] matmul @ operator precedence

Mark Dickinson added the comment: Gah! Forgot that my post would reset this issue to open. I'm going to close here, since this would be a sufficiently big and unlikely change that it's not going to happen without a python-ideas/python-dev discussion. --

[issue33390] matmul @ operator precedence

Mark Dickinson added the comment: [Steven] > please take the idea to the numpy and/or Python-Ideas mailing lists for > further discussion: But please do read through the previous discussions before starting a new one! See the links in PEP 465, and particularly

[issue33390] matmul @ operator precedence

Steven D'Aprano added the comment: Precedence issues when dealing with units is unavoidable, I think. The units program on Linux/Unix has similar issues, and they write their own parser and choose their own precedence.

[issue33390] matmul @ operator precedence

Eric V. Smith added the comment: Operator precedence cannot change without breaking existing code. -- nosy: +eric.smith type: behavior -> enhancement versions: +Python 3.8 -Python 3.5 ___ Python tracker

[issue33390] matmul @ operator precedence

New submission from fabrice salvaire : I use the new matmul @ operator to implement units, for example 1@u_s for 1 second ( see alpha state implementation at https://github.com/FabriceSalvaire/PySpice/tree/master/PySpice/Unit ). It looks cool, but unfortunately