2 ms·

I'm curious to see how it will pan out in practise, but I'm not getting my hopes up. I made a flake8 plugin to forbid assignment expressions: https://github.c

by korijn 8y ago

I'm curious to see how it will pan out in practise, but I'm not getting my hopes up. I made a flake8 plugin to forbid assignment expressions: https://github.com/Korijn/flake8-assignexp https://github.com/Korijn/flake8-assignexp Will be released once python 3.8 is out and I can test it.

geoelectric 8y ago
That seems unnecessarily reactionary, but ok. I agree with the post you're responding to that having a completely separate token for inline assignment fixes the majority of issues that have historically come up with it (which mostly come down to forgetting an = in the ==). Might be worth feeling out the trajectory of the feature before proactively banning it from codebases you control.
- korijn 8y ago
  You're right. Like I said, I'm curious to see how it will pan out, but I'm not getting my hopes up. I'm just not a fan of this new syntax. :) IMHO null-safe navigation operators like ?. and ?[] are much more important to have.