Jimmy Jia

There are, but my thought there was that those cases were likely to be rare, and more context-specific – `getData` and `render` ought instead to be idempotent. This is specifically...

If you're not using nested routes, then the choice of router framework doesn't make much of a difference. You wouldn't have even really needed react-router-relay. That said, the route configuration...

It looks like support was added in https://github.com/facebook/pyre-check/commit/64487f55ce9fba75d894701eb35b23a147743c46. Should this issue be closed out?

PEP 8 explicitly enjoins against the space between the comma and the closing paren on single-element tuples: https://www.python.org/dev/peps/pep-0008/#pet-peeves This is one of many inane YAPF-isms.

Development does seem to have slowed down a lot. black is gaining a ton of traction in the Python space these days.

PEP 257 requires double quotes for docstrings. It also requires a blank line after the docstring for classes, but not for functions.

The comma syntax in `except` is a Python 2.5 thing so probably it's dead. The nested `with` statements do arise in real code, though: https://github.com/tensorflow/models/blob/1887a5fe187c8ab9f623cd91b74fc8432ce76d6f/research/slim/nets/mobilenet_v1.py#L199-L200 Part of the issue is...

Makes you wish they didn't drop `contextlib.nested` in Python 3. `ExitStack` can give the same semantics but it's more annoying to use.

YAPF's output here is good for a giggle, though: ```python # In: with \ Foo() as foo, \ Foo() as foo_2, \ Bar( long_argument, long_argument, long_argument, long_argument, long_argument, ) as...

it’s pycodestyle now y’all should talk to the @pycqa folks, especially @sigmavirus24