Daniel Hahler

Agreed. The setting would be only a workaround. So basically jedi-vim would have to consider and submit any unchanged (Python) buffers. I think this does not only affect renaming, but...

> the one you're working on is always parsed with the changes Yes, I knew - and that is nice of course! But other unsaved ones are not handled that...

But if jedi-vim would be submitting/providing contents of changed buffers (instead of letting Jedi read them from disk), this wouldn't have to abort, but would just work. That's what this...

> setuptools_scm Have you considered using https://github.com/codrsquad/setupmeta instead? (I often found setuptools-scm fragile / rather bad at error handling.)

> I'm not sure to follow what is wrong with #59, is there a problem with the Pytest workaround provided? Some exceptions that are displayed while they should not? It...

> but can't be easily fixed without extending the Logger api You could set it via private methods directly. Otherwise your information is what I've seen also. My plan for...

> I don't think we need coverage of the tests/ folder. It is useful to see if tests are not executed/run accidentally.

Regarding the test example, you could use an assert for the attribute name and raise AttributeError always? Given the extra assertion this would improve the test. As for `if foo`:...

We could maybe split this into two PRs: one for covering tests and then another for the branch coverage, which could be worked on over time then?

> Sorry, I struggle visualizing your solution. I need to simulate the fact that `tm_gmtoff` and `tm_zone` doesn't exist on some paltform, but other attributes are perfectly fine. Then it...