DylanYoung

See https://github.com/PyCQA/pep8-naming#options for an alternate implementation that can leave a lot of these decisions up to the user.

I like the check (because there is never a need to `assert False` that I can see), but can certainly get behind modifying the advice ("replace this with by raising...

I also like the idea of catching places where AssertionError is caught, but it should be a separate check and disabled by default (it's valid in many cases: e.g. a...

Here's how pep8-naming handles it: https://github.com/PyCQA/pep8-naming#options

@wolverdude I had to look at the code to see what exactly this was referring to and I understand now, you use some heuristic to pull multiple object definitions from...

To start off the deprecation, you could make `--delimiter` required for this functionality.

Oh this is an interesting one. What about a ``--infer-patterns`` optional argument that takes a list of json paths? It could construct a minimal DFA for those keys and convert...

@wolverdude Actually, I think that's fine for my use case. I was actually looking for yaml input (to generate a json schema for our yaml changelog to work with vs...

Sweet. I'm in rough living situation right now, but I'll come back to this after I'm situated if noone picks it up before then :) On Sun., Jan. 12, 2020,...

Basically the idea is that if the same "subschema" is encountered more than X times, it would be encoded in the resulting schema as a definition and referenced where it...