Jon Parise

pymemcache clients don't support concurrent, multithreaded usage out-of-the-box. They don't do any internal locking, etc. Only the client pool is thread-safe. If you are accessing a client object from multiple...

I can't give a complete answer without knowing more details about your code, but generally: 1. You can share a pymemcache client across multiple threads if you add your own...

I think I'd go the Schema route. This level of configuration is more tightly coupled to the representation of the API than, say, a pluggable JSON module, which is an...

Totally agree. My `get_env/3` comment was more about customizing the innards of the translator implementation, not making the translator swappable, but I should have been clearer.

We actually now have code that attempts to traverse as much of the class hierarchy as is possible (given the AST's limitations). We use it to find `Exception` subclasses. https://github.com/PyCQA/pep8-naming/blob/9adbbc4a6248db25eff2c7bc13b090b1d83ffd04/src/pep8ext_naming.py#L300-L316...

`ignore-names` now also applies to N806, N815, and N816 checks as of #96.

> Then I propose: > > * When using `from package import item as name`, enforce that `item` and `name` have the same case type. This can be kept in...

> > Your second proposed rule feels closest in spirit to PEP 8. I'm less sure about the first one. > > What are you not sure about the first...

We could consider changing the rule to allow a mixed-case variable name (left-hand side) if its being assigned to a mixed-case name (right-hand side).

@sigmavirus24 I think that's a fine position to take, too. I imagine these cases are rare in practice, so it's reasonable to ask users to annotate them with `# noqa`.