4 ms·

For me virtualenv+requirements is good enough. The only feature of Poetry that I miss is the ability to create wheels without a setup.py. But I don't create whe

For me virtualenv+requirements is good enough. The only feature of Poetry that I miss is the ability to create wheels without a setup.py. But I don't create wheels when writing backend code. So I only use Poetry for working with packages.

miguendes 5y ago
Poetry does create wheels without a setup.py. In fact, on my last job we got rid of all setup.py we had in favour o poetry. It cannot replace all setup.py use cases, but for pure python packages it can replace it completely.
- nromiun 5y ago
  I mean I miss that feature of Poetry when working with pip+venv.
sonthonax 5y ago
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.
- miguendes 5y ago
  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.
  - sonthonax 5y ago
    But I can’t do it from pip to another poetry package. I have to be using poetry for it.
    - miguendes 5y ago
      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.
- nromiun 5y ago
  True. I guess I just prefer pyproject.toml, it is definitely more minimal for my use cases.