This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steven.daprano
Recipients FabriceSalvaire, eric.smith, steven.daprano
Date 2018-04-30.00:10:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525047013.41.0.682650639539.issue33390@psf.upfronthosting.co.za>
In-reply-to
Content
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.

https://www.gnu.org/software/units/manual/html_node/Operators.html

As Eric says, we can't change the precedence of the @ operator easily, if at all. It would likely require at least one full release (3.8) with a warning, or a future import, and frankly if the numpy community is against it you'll have zero chance of it happening. (On the other hand, if they're in favour of it, you'll have a good chance.)

If you still want to pursue this idea further, please take the idea to the numpy and/or Python-Ideas mailing lists for further discussion:

https://www.scipy.org/scipylib/mailing-lists.html

https://mail.python.org/mailman/listinfo/python-ideas

but for now I'm going to set the issue to pending.
History
Date User Action Args
2018-04-30 00:10:13steven.dapranosetrecipients: + steven.daprano, eric.smith, FabriceSalvaire
2018-04-30 00:10:13steven.dapranosetmessageid: <1525047013.41.0.682650639539.issue33390@psf.upfronthosting.co.za>
2018-04-30 00:10:13steven.dapranolinkissue33390 messages
2018-04-30 00:10:11steven.dapranocreate