-
There are multiple files (setup.py, setup.cgfg and pyproject.toml). Collapse to pyproject.toml and remove setup.py if not needed. The current. I think using poetry would also eliminate requirements.tx…
-
-
It looks like it's time to migrate from setup.py to pyproject.toml.
The conda-forge linter is requesting that we specify a pip backend, which we can't do for the legacy backend used for setup.py. […
-
New modules for the package need to be manually added to the pyproject.toml. There should be some automatic discovery as pointed out by @lucianopaz in PR #803
-
In https://github.com/ckan/ckan/pull/6620 setup.py was largely simplified but still some bits remain in old setup.py files. Now with lates pip and setuptools installing extensions as editable for deve…
-
Seems highly recommended now per [Python Packaging User Guide](https://packaging.python.org/en/latest/).
See https://packaging.python.org/en/latest/guides/modernize-setup-py-project/#modernize-setu…
-
The package currently has both a `pyproject.toml` file and a `setup.py` file in place. The former contains the majority of the package specification; the latter, content for converting a single `.pyx…
-
Hi, would it be possible/realistic to configure [StubInfo](https://github.com/Jij-Inc/pyo3-stub-gen/blob/16eb5d3bf133d73885afa4b4eaa649991035a974/pyo3-stub-gen/src/generate/stub_info.rs#L5-L9) and [St…
-
-
change from `setup.py` to `pyproject.toml`.
The pyproject.toml seems to have a bit more flexibility and more features