Jakob Schnitzer

> The reason is this: pip needs to know about all the other packages that it is installing, so it can resolve dependencies correctly. If it doesn't know about the...

Yes, the timing of some of these last two PRs was a bit unfortunate with relation to your PRs, sorry about that again. Except for the `no-self-use` one (where I'd...

Nice :) One thought: I think we could drop support for Python 3.6 (EOL since December) before adding widespread type annotations, which would allow us to do `from __future__ import...

Thank you for this PR :) I pretty much agree with the following: > [..] I'd vote for Expression.{isin,isnotin} and vote against Query.isnot.

I've fixed the error on the JS side in #900 I don't really see a good reason for having a checkboxes without any choices, I think it would also be...

I've been using Lektor for a few years and it's sad to see the project stagnate :( I haven't contributed any code so far but I've opened some PRs now...

Thank you @dairiki for getting this issue going again and pushing for a release (and all your other recent contributions as well). I think between the two of us, we've...

> What more is it going to take to get a release out the door? 3.2.2 is out already ;) (https://pypi.org/project/Lektor/) But I agree that we should also soon have...

> I don't have the solution, but it would sure be nice to get Lektor out of the package-management business altogether. I couldn't agree more. This is PR is just...

I'm with you that the `--target` option is the bigger culprit, but of the two problematic option it is the one we can't drop without creating an even bigger mess...