No, even if it isn't installed, poetry does add it as a dependency to poetry.lock. So there is no way to not end up having it installed in production if we use dkimpy - it will always end up in poetry.lock.
I'm not sure how poetry works, why it is adding it as a dependency. But in version of dkimpy 1.0.5, it was adding dnspython as a transitive dependency instead.
The solution would be to use extras:
pip install dkimpy - would install whatever is already installed
pip install dkimpy[dnspython] - would require dnspython, py3dns would not be an option
I don't know if that is possible. But it would help.
If it is a poetry issue, I don't know what to report to them exactly.
No, even if it isn't installed, poetry does add it as a dependency to poetry.lock. So there is no way to not end up having it installed in production if we use dkimpy - it will always end up in poetry.lock.
I'm not sure how poetry works, why it is adding it as a dependency. But in version of dkimpy 1.0.5, it was adding dnspython as a transitive dependency instead.
The solution would be to use extras:
pip install dkimpy - would install whatever is already installed
pip install dkimpy[dnspython] - would require dnspython, py3dns would not be an option
I don't know if that is possible. But it would help.
If it is a poetry issue, I don't know what to report to them exactly.