Jeff Dairiki

@yagebu I do think this is the way of the future. Much cleaner, more stable. Great work. We should almost definitely work on moving Lektor out of the package management...

> FYI, my fix for `marshmallow_dataclass` has been cherry-picked into [lovasoa/marshmallow_dataclass#211](https://github.com/lovasoa/marshmallow_dataclass/pull/211) and merged to master. Unless reverted, the fix fill will be available with any next release (which I have...

I've gone ahead and removed the `lektor dev publish-plugin` command.

I've updated the plugin quickstart template to make it PEP517 compliant. I moved the setuptools configuration to `setup.cfg`. I considered it to `pyproject.toml` but held off since the setuptools docs...

> Could we also add the plugin venv path to `lektor project-info`? The path is printed when plugins are loaded, but that would be nice too. Since it's now a...

> I found a related bit of code I think makes some sense to clean up with this PR. > > https://github.com/dairiki/lektor/blob/bug.865-local-plugin-installation/lektor/pluginsystem.py#L203 > > That doesn't seem to be a...

> I found a related bit of code I think makes some sense to clean up with this PR. > > https://github.com/dairiki/lektor/blob/bug.865-local-plugin-installation/lektor/pluginsystem.py#L203 PR #1073 does away with this use of...

> Could we also add the plugin venv path to `lektor project-info`? The path is printed when plugins are loaded, but that would be nice too. Since it's now a...

> A plugin's `install_requires=["Lektor"], ` can be problematic because it can cause a reinstallation of Lektor. Surely a conundrum we'd all love to see resolved! Especially since, really, plugins do...

> * I think it's best that Lektor itself and what Lektor uses to manage plugins be the same tool. I'm not convinced (yet) that that's of much importance. For...