Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But you still need a pyproject.toml, which is just a setup.py in a different form.

One gripe with pyproject.toml is that I can’t do editable installs (i.e ‘pip install -e path/to/package/‘) with it. Highly annoying when trying to patch packages.



You actually can but it's not documented I guess. I remember finding it when I dug the source code.

[tool.poetry.dependencies] my-package = { "path" = "path/to/package", develop = true }

This way you can patch my-package and poetry will always install the latest state of it.


But I can’t do it from pip to another poetry package. I have to be using poetry for it.


Ah got it, I see what you mean now. In cases like this I had to build the wheel and install it which is not great indeed.


True. I guess I just prefer pyproject.toml, it is definitely more minimal for my use cases.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: