Arun Babu Neelicattu

Rebased this. While the code works, and is an exact port of current poetry@master, the functionality introduced via groups is a bit ambiguous at present.

Thanks @riconnon I will see what the other's on the core team think about this in general.

I'm a bit unclear on what is being solved here. Poetry's editable builder has nothing to do with poetry-core's wheel builder. No wheel is built during that process. A temporary...

Don't think this is a good idea. Since this will fail isolated builds. ```sh python -m pip build python -m build . python -m pip install --use-pep517 . ```

Oops. I meant `python -m pip install build` :) On reading up a bit, I am inclined to say that we should favour an in-place build in general. This means...

As for testing I would recommend adding a new fixture in https://github.com/python-poetry/poetry-core/tree/master/tests/fixtures and that includes sources from `../` and run it through a complete build, sdist build, and wheel build....

> What is the purpose of that check? I can clearly see that it's important, it was added for a reason, I just don't understand what problem it solves This...

I am not sure if this is something we should do. While this produces reproducible builds on the same machine, it can lead to different content hashes on a different...

@python-poetry/core @python-poetry/triage Would apprecaite feedback on this. We need to disable auto setup generation, this was originally planned for Poetry 1.2 as it was deprecated in Poetry 1.1. I am...

@gaby think I got the builds to pass now. I am not sure how to debug the e2e tests as I do not really use ignite. I came here trying...