Please, Mike, can you stop? The race is over and your horse has lost. I
really value all the input I've received during the months of discussion
(including your research into what other languages do), but in the end my
"evaluation function" (to use somewhat hip lingo :-) is different from
yours.
On 2018-07-05 10:52, Ivan Pozdeev via Python-Dev wrote:
>
Perhaps, however I'm not advocating using "EXPR as NAME" with "with" as it
wouldn't be useful enough, only limited to if/while/comp.
-Mike
___
Python-Dev mailing list
Python-Dev@python.org
On Thu, Jul 05, 2018 at 08:52:24PM +0300, Ivan Pozdeev via Python-Dev wrote:
> * Same goes for `except`: doesn't accept expressions, same semantic.
py> def make_exception(arg):
... return ValueError if arg else TypeError
...
py> expr = [make_exception]
py> try:
... 1+"1"
... except
On 05.07.2018 3:22, Chris Angelico wrote:
Python uses "as NAME" for things that
are quite different from this, so it's confusing
I wrote in
https://mail.python.org/pipermail/python-dev/2018-June/154066.html that
this is easily refutable.
Looks like not for everybody. Okay, here goes:
The
On 2018-07-05 04:28, Ivan Pozdeev via Python-Dev wrote:
This is as intended.
I wanted to show my summary and Chris' refuttal, with links to both original
posts. Because my letter is much shorter than the originals while carrying the
same message. Also to show that I've made the same mistake,
On 2018-07-04 17:22, Chris Angelico wrote:
- the "if expr as name:" syntax is able to handle only the tiniest
proportion of cases, because many MANY situations require a condition
after that. You can't write this, for instance:
if f(x) as spam < 0:
print(spam)
The original use cases
On 2018-07-04 23:20, Steven D'Aprano wrote:
It simply isn't true that modern languages are moving away from
assignment expressions. Some are. Some aren't. Even those that don't
support assignment expressions in general usually support special syntax
to allow it in a few contexts.
The older
On 05.07.2018 9:20, Steven D'Aprano wrote:
On Thu, Jul 05, 2018 at 05:33:50AM +0300, Ivan Pozdeev via Python-Dev wrote:
And https://mail.python.org/pipermail/python-dev/2018-June/154160.html
disproves the "chosen often these days in new languages".
Ivan, I think you may have linked to the
On Thu, Jul 05, 2018 at 05:33:50AM +0300, Ivan Pozdeev via Python-Dev wrote:
> And https://mail.python.org/pipermail/python-dev/2018-June/154160.html
> disproves the "chosen often these days in new languages".
Ivan, I think you may have linked to the wrong page. That page was Chris
kindly
On 05.07.2018 2:52, Mike Miller wrote:
Recently on Python-Dev:
On 2018-07-03 15:24, Chris Barker wrote:
> On Tue, Jul 3, 2018 at 2:51 PM, Chris Angelico > On Wed, Jul 4, 2018 at 7:37 AM, Serhiy Storchaka
>
> > I believe most Python users are not
> > professional programmers --
On Wed, Jul 04, 2018 at 04:52:54PM -0700, Mike Miller wrote:
> Additionally, I have noticed a dichotomy between prolific "C programmers"
> who've supported this PEP and many Python programmers who don't want it.
Prolific C programmers like me, hey?
*shakes head in a combination of amusement
On Thu, Jul 5, 2018 at 9:52 AM, Mike Miller wrote:
> Compromise:
>
> Fortunately there is a compromise design that is chosen often these days in
> new languages---restricting these assignments to if/while (potentially
> comp/gen) statements. We can also reuse the existing "EXPR as NAME" syntax
>
12 matches
Mail list logo
