I am trying to install the pytorch3d library directly from Github via poetry. I noticed, however, that apparently this library is not PEP-517 compliant. It has a build-time dependency on torch but this dependency is not declared in the pyproject.toml file of the project. From what I understand, it is now a Python packaging best practice that libraries should specify their build dependencies explicitly.
The problem arises when I attempt to install this library via poetry, as poetry is very restrictive and simply fails to perform the installation. What I find concerning is that this happens very often with poetry, while in such cases pip has no issue to install the library whatsoever.
I start to assume that poetry is simply not suited for dependency management if the project involves a lot of non-standard, third-party, and potentially legacy, libraries. In a development workflow it is often not possible to only use dependencies that are totally up-to-date in PEP standards, hence I find that such restriction is a serious issue with poetry.
My questions:
- Is there any workaround to install such "problematic" packages?
- If I need to resort to using pip for such packages, would that mean the end of poetry's dependency resolution capabilities, since some of the packages would be installed via poetry and others via pip?
- Should I even use poetry at all, or would I be better off with something else?