[04:41:04] <famubu> How can we build a package, if we are using setuptools without a setup.py but with only pyproject.toml and setup.cfg? When `setup.py` was there, we used to do `python3 setup.py sdist wheel` as per the tutorial in the docs. How do we do this when there is no setup.py? In the pyproject.toml, under `build-system`, I added `requires = ["setuptools>=40.8.0", "wheel"]` and `build-backend = "setuptools.build_meta"`.
[04:45:14] <famubu> Is there a sample project that doesn't have setup.py that we can checkout?
[07:41:10] <famubu> Oh, I didn't know pep517.build was not meant for production environments. So that means, for production, we better keep using setuptools with setup.py? Even if pyproject.toml is there?
[07:41:24] <famubu> And I had not heard of python-build. Thanks for pointing that out.
[07:50:57] <famubu> Suppose I have a package that's currently using setuptools without pyproject.toml, how can I port it to use poetry (or flit)? I never tried flit but tried to port a setup.py package to poetry. Couldn't figure out a way to do it.
[10:46:29] <FFY00> both pep517.build and python-build are usable right now
[10:46:55] <FFY00> but I'd wait for a new python-build release for a more complete CLI
[10:47:17] <FFY00> right now, pep517.build builds in a semi-isolated environment
[10:47:33] <FFY00> python-build does not isolate anything
[10:47:55] <FFY00> the new release will build in full isolation by default, allowing you to apot out if you want