Francisco Puga

There are also two flake8 plugins that are related to this feature, but it will be nice to have it in pep8-naming: - [flake8-module-name](https://pypi.org/project/flake8-module-name/). A flake8 plugin for testing PEP-8...

Is working fine for me. Can you provide a [fiddle](https://plnkr.co/edit/?p=preview&preview) or more info about your case.

I check that in my tests and see no real difference. ```text f_table_name │ f_geometry_column │ type │ srid │ coord_dimension ═════════════════════════════════╪═══════════════════╪═════════════════╪═══════╪═════════════════ old_table │ the_geom │ MULTIPOLYGON │ 25829 │...

I've created a reproducible example. Just note that my testing environment is PostgreSQL v9.6 and PostGIS v2.5. Only one schema, with two tables. `old_table` has been created in the past...

The patch is working for me. It will be awesome if you can find some time to integrate it @Arcanemagus. :)

Can this ticket be reopened? I'm still getting a `WPS440` in code like the shown in the first comment with version 0.15.3 ```python for widget in self._widgets: await widget.update() ......

I fall into this case also. Just for the record, to launch the tool only against .py files I execute the tool two times in this way: autopep8 --diff --recursive...

I also fall into this. Thanks a lot for the workaround.

I agree. Right now is very hard to see the cursor. If it is preferible keep the same "color" but make it a litle brigth you can try with `#bc39b7`...

It seems that the original motivation was explained in #5 but i agree that it will be nice have it in the README. Also, i don't understand the example in...