Randy Döring

Probably caused by #103, which replaced `build_venv()` with `create_venv()`. Unfortunately, I will not have time to take a closer look within the next few weeks. Maybe, @BrandonLWhite can help.

> We already have self referring to the global Poetry installation and IMHO this will be confusing if one self was global and one per project. Yeah, that has already...

It just belongs together because both are requirements for Poetry it*self*. By the way, when running `poetry self show plugins`, both, global plugins and project plugins will be displayed. Actually,...

@johnthagen Since you seem to be interested in this PR and have already given valuable input in various user interfacing issues, I would like to ask for your opinion: `self`...

Although this could come before `[project]` support, I think both will be released together. However, even with `[project]` support, the fields in `[tool.poetry]` are still there (although many of them...

@johnthagen Thanks for your input. One thing that came to my mind: Is `requires-plugins` unambiguous enough or is `requires-poetry-plugins` better?

I updated the PR from `tool.poetry.self.version` and `tool.poetry.self.plugins` to `tool.poetry.requires-poetry` and `tool.poetry.requires-plugins`.

After taking a closer look at it, here are a few more arguments: default to "only sdist" - When installing a wheel with includes, the includes are unpacked straight into...

@johnthagen Since you often give good advice on usability and this is a difficult choice, I'd appreciate your opinion. (In case, you have never used this feature and have no...

> What would be needed to get this Pull Request going? It requires a Poetry release that includes https://github.com/python-poetry/poetry/pull/9427. That will be https://github.com/python-poetry/poetry/issues/9448.