In reply to @Evidlo:matrix.org
I'm going to merge that one in before yours because I feel bad about closing a PR that I let sit for too long

In reply to @Evidlo:matrix.org
I'm going to merge that one in before yours because I feel bad about closing a PR that I let sit for too long

As I understand, setuptools is only about building packages and for the dependency management and isolation you have to use other tools like venv, pip, pipenv, etc.
In my opinion it is more convenient to use poetry (or maybe PDM) for that especially because they gives you additional things, like lock files, speed improvements (https://dev.to/frostming/a-review-pipenv-vs-poetry-vs-pdm-39b4) and better dependency resolutions.

For me personally (as a beginner python developer) it was simpler to just create pyproject file and use poetry than figuring alternative ways to install and manage dependencies in your library. I believe it could be the same for other newcomers.

using poetry is as simple as that:

1. install poetry itself
2. poetry install to install the deps in the automatically created venv
3. poetry run ... whatever you need to run tin the venv (or poetry shell and then run that in the activated venv without prefix)

I don't see steep learning curve here.

In a nutshell, if that's isn't valuable for you - it is OK, it is your choice, just decline my PR plz, so it wouldn't hang there.

Alternatively, I could change it to use PDM instead of poetry. It is complaint with PEP 517 (A build-system independent format for source trees). I am not sure yet, but I suppose you can use just pip to install the dependencies from the pyproject file and don't need to install PDM for that purpose. Ofc. you wouldn't use the lock file in that case.

As I understand, setuptools is only about building packages and for the dependency management and isolation you have to use other tools like venv, pip, pipenv, etc.
In my opinion it is more convenient to use poetry (or maybe PDM) for that especially because they gives you additional things, like lock files, speed improvements (https://dev.to/frostming/a-review-pipenv-vs-poetry-vs-pdm-39b4) and better dependency resolutions.

For me personally (as a beginner python developer) it was simpler to just create pyproject file and use poetry than figuring alternative ways to install and manage dependencies in your library. I believe it could be the same for other newcomers.

using poetry is as simple as that:

1. install poetry itself
2. poetry install to install the deps in the automatically created venv
3. poetry run ... whatever you need to run tin the venv (or poetry shell and then run that in the activated venv without prefix)

I don't see steep learning curve here.

In a nutshell, if that's isn't valuable for you - it is OK, it is your choice, just decline my PR plz, so it wouldn't hang there.

Alternatively, I could change it to use PDM instead of poetry. It is complaint with PEP 517 (A build-system independent format for source trees). I am not sure yet, but I suppose you can use just pip to install the dependencies from the pyproject file and don't need to install PDM for that purpose. Ofc. you wouldn't use the lock file in that case.

As I understand, setuptools is only about building packages. For the dependency management and isolation you have to use other tools like venv, pip, pipenv, etc.
In my opinion it is more convenient to use poetry (or maybe PDM) for that especially because they gives you additional things, like lock files, speed improvements (https://dev.to/frostming/a-review-pipenv-vs-poetry-vs-pdm-39b4) and better dependency resolutions.

For me personally (as a beginner python developer) it was simpler to just create pyproject file and use poetry than figuring alternative ways to install and manage dependencies in your library. I believe it could be the same for other newcomers.

using poetry is as simple as that:

1. install poetry itself
2. poetry install to install the deps in the automatically created venv
3. poetry run ... whatever you need to run tin the venv (or poetry shell and then run that in the activated venv without prefix)

I don't see steep learning curve here.

In a nutshell, if that's isn't valuable for you - it is OK, it is your choice, just decline my PR plz, so it wouldn't hang there.

Alternatively, I could change it to use PDM instead of poetry. It is complaint with PEP 517 (A build-system independent format for source trees). I am not sure yet, but I suppose you can use just pip to install the dependencies from the pyproject file and don't need to install PDM for that purpose. Ofc. you wouldn't use the lock file in that case.

As I understand, setuptools is only about building packages. For the dependency management and isolation you have to use other tools like venv, pip, pipenv, pipx, etc.
In my opinion it is more convenient to use poetry (or maybe PDM) for that especially because they gives you additional things, like lock files, speed improvements (https://dev.to/frostming/a-review-pipenv-vs-poetry-vs-pdm-39b4) and better dependency resolutions.

For me personally (as a beginner python developer) it was simpler to just create pyproject file and use poetry than figuring alternative ways to install and manage dependencies in your library. I believe it could be the same for other newcomers.

using poetry is as simple as that:

1. install poetry itself
2. poetry install to install the deps in the automatically created venv
3. poetry run ... whatever you need to run tin the venv (or poetry shell and then run that in the activated venv without prefix)

I don't see steep learning curve here.

In a nutshell, if that's isn't valuable for you - it is OK, it is your choice, just decline my PR plz, so it wouldn't hang there.

Alternatively, I could change it to use PDM instead of poetry. It is complaint with PEP 517 (A build-system independent format for source trees). I am not sure yet, but I suppose you can use just pip to install the dependencies from the pyproject file and don't need to install PDM for that purpose. Ofc. you wouldn't use the lock file in that case.

As I understand, setuptools is only about building packages. For the dependency management and isolation you have to use other tools like venv, pip, pipenv, pipx, etc.
In my opinion it is more convenient to use just one tool for that (poetry or maybe PDM) especially because they gives you additional things, like lock files, speed improvements (https://dev.to/frostming/a-review-pipenv-vs-poetry-vs-pdm-39b4) and better dependency resolutions.

For me personally (as a beginner python developer) it was simpler to just create pyproject file and use poetry than figuring alternative ways to install and manage dependencies in your library. I believe it could be the same for other newcomers.

using poetry is as simple as that:

1. install poetry itself
2. poetry install to install the deps in the automatically created venv
3. poetry run ... whatever you need to run tin the venv (or poetry shell and then run that in the activated venv without prefix)

I don't see steep learning curve here.

In a nutshell, if that's isn't valuable for you - it is OK, it is your choice, just decline my PR plz, so it wouldn't hang there.

Alternatively, I could change it to use PDM instead of poetry. It is complaint with PEP 517 (A build-system independent format for source trees). I am not sure yet, but I suppose you can use just pip to install the dependencies from the pyproject file and don't need to install PDM for that purpose. Ofc. you wouldn't use the lock file in that case.