Pin used dependencies with PipLock

[szszszsz]

To introduce automatic pinning, e.g. with Pipenv tool.
@daringer : what do you think?

[daringer]

Yap, sounds good
already using a hackish solution via dev-requirements.txt

[dvzrv]

As you are already using pyproject.toml, why not use poetry instead of pipenv?

[szszszsz]

Hi @dvzrv !

Thank you for the suggestion! Last time I have checked poetry had own issues, hence I wanted to stay with the one I know until the other matures. Worth looking again on poetry definitely.

[szszszsz]

@dvzrv By the way, why do you advocate for poetry?
Is it only because of the pyproject.toml file, or do you have some other things in mind?

[dvzrv]

@dvzrv By the way, why do you advocate for poetry?
Is it only because of the pyproject.toml file, or do you have some other things in mind?

It's mainly because it (currently) seems to be one of the few "all-in-one" solutions (pipenv had so many awkward flaws - e.g. pypa/pipenv#2364 - and yes, to my knowledge does not support pyproject.toml). It's fairly convenient, because it can:

• pin your dependencies
• manage your venvs
• allow easy interaction with venvs
• allow for creation of source tarballs or wheels
• allow for tests with tox on several python interpreter versions (but it does not auto-handle e.g. pyenv for you - which IMHO is good)
• publish to pypi

On the downside: Its use of venvs is not necessarily super fast, but then again, venvs are generally not super fast (it's the same for pipenv). ;-)