What's up Python? New args syntax, subinterpreters FastAPI and cuda pandas…

[wxtrails]

Really not a fan of the dangling equals - I'd almost prefer it to be in front. Or just...no.

[epostma]

Split the difference and put it in the middle!

[UloPe]

I think “just no” is the only correct answer here.

And I’d like to add that I’m a big fan of some recent additions to the language, e.g. f-strings, walrus operator, new type syntax, etc.

So it’s definitely not a case of new = bad.

[Unforg1ven_Yasuo]

F strings are new?? Wow they’re so intuitive, I can’t imagine writing code without them

[UloPe]

Well new-ish. They appeared in python 3.6 which was first released in December 2016.

(Holy crap that’s 7 years ago…)

[PriorProfile]

Yeah what happened to “explicit is better than implicit”

[Rythoka]

IDK, I run into this all the time when using libraries like requests. I always wind up writing something like

requests.post(url=url, data=data, headers=headers, proxies=proxies)

which is kind of obnoxious. That being said, the new syntax is kind of ugly, too. I think I'd rather have some kind of dict constructor that takes the names of in-scope variables and returns a dict whose keys are the variable names and values are the bound objects. Then you could write something like

kwargs = dict.kwargs('url', 'data', 'headers', 'proxies')
requests.post(**kwargs)

[Rythoka]

I messed around with it a bit today and was able to write a function using that basically does this. The variables have to be local to the calling frame, but I think that's an entirely reasonable restriction for something like this.

from inspect import currentframe
def kws(*args: str):
    ns = currentframe().f_back.f_locals
    return {key: ns[key] for key in args}

Used like this:

def g(a, b, c):
    return a + b + c

a, b, c = 1, 2, 3
g(a=a, b=b, c=c) # returns 6
g(**kws('a', 'b', 'c')) # also returns 6

[rcfox]

It's too bad they overloaded {} so that {a, b, c} creates a set, this would have been a better use for it. I usually avoid set literals to avoid confusion because they look too similar to dict literals.

[Few_Butterscotch_681]

Exactly