4 ms·

I'm not saying they are, I don't think I've used the language enough to be able to tell what's pythonic and what's not. It's just that I think the language supp

• StavrosK 10y ago
  > why defining a function and calling it right after? Documentation.
  • coldtea 10y ago
    You could have named closures, so that's hardly a valid reason.
    • xapata 10y ago
      We prefer to have only one obvious way to do it. The more good techniques in existence, the less there's a clear sense of "Pythonic". It's just a preference. Many tasks have more than one obvious way. But if you're asking to add a new feature, you should explain why it's worth the downside of adding yet another way to do it.