Frank Harrison

Having used git since ~0.9, I had to work out that husky does things slightly differently from what I was used to (e.g. `pre-commit`); Husky's way is much better and...

There are 3 issues here if I'm reading it correctly: 1. Deprecated objects 2. Duplicate names (called aliases here) 3. Best practice issues Whilst they are vaguely related to imports...

> Actually, just best practice issues of importing from `collections` over `typing` where possible. "Actually," across the entire thread, the three issues are mentioned. > Another kind of import rewriting...

> Personally, I use isort in my workflow as a tool with the _single responsibilty_ of **standardizing import lines** Gotcha 👍 The issue title and the example do not clearly...

This is a linting issue and `isort` shouldn't fix this automatically, `isort` is doing the right thing and this issue should be closed. Let me explain: Same-scope ordering is (pretty...

According to PEP 420 this issue is about [Nested Namespace Packages](https://peps.python.org/pep-0420/#nested-namespace-packages). It seems isort doesn't yet have any explicit handling for that type of package ([auto_identify_namespace_packages](https://pycqa.github.io/isort/docs/configuration/options.html) doesn't seem to cover...

See #33 for a temporary workaround.

@paescuj couldn't agree more but the idea was rejected here #1166 and here #1167. Personally, I have decided to stop contributing to this project.

Have a look at `.nyc_output/out.json`.

What is happening with this bug? Bug #1965 is still not fixed but has been closed.