Kasra Vand added the comment:
Due to the discussion in following SO question
https://stackoverflow.com/questions/55933956/what-does-a-star-asterisk-do-in-f-string/55934472#55933956
and the inconsistency of the source behaviour with the documentation I think
using `"*" or
New submission from Kasra Vand :
Due to the discussion in following SO question
https://stackoverflow.com/questions/55933956/what-does-a-star-asterisk-do-in-f-string/55934472#55933956
and the inconsistency of the source behaviour with the documentation I think
using `"*" or
Change by Kasra Vand :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue33344>
___
___
Python-bugs-list
Kasra Vand added the comment:
I think this will contradict to Python's operators precedence. What I mentioned
seems like you're passing the number as an argument to `not`, and this is while
`not` is not a function. There is an `operator.not_` function that does the
same job a
Kasra Vand added the comment:
Thanks, Indeed. But my question is more about the syntax and why it's not that
straight? The reasons for that is because Python is known as a scientific
programming language and many people come with mathematical background and may
want to use this ki
Kasra Vand added the comment:
This may seem not very useful while except 0 for other numbers it returns False
but one may want to use another proposition inside `not` that can use either 0
or a nonzero number. Also, in this case we can form more comprehensive logical
propositions
New submission from Kasra Vand :
Logical Negation of integers in Python always returns a Boolean result which
can be achieve using `not`. Sometimes it's necessary to use this result
directly in a proposition within a list comprehension (mostly). But if we use
`not` directly in such arith
