Since pyproject.toml does not record any version restrictions, we need poetry.lock to define the currently used versions. Otherwise, we cannot guarantee that a newly created template instance will run. For example, fastapi-complete doesn't work with databases 0.8.0 yet but this version will be used during the template instantiation anyway because of the lack of a restriction in pyproject.toml or in poetry.lock.
I prefer to keep pyproject.toml the way it is, so it will be possible to run poetry update to update all dependencies to their latest versions anytime.
Since
pyproject.toml
does not record any version restrictions, we needpoetry.lock
to define the currently used versions. Otherwise, we cannot guarantee that a newly created template instance will run. For example,fastapi-complete
doesn't work withdatabases 0.8.0
yet but this version will be used during the template instantiation anyway because of the lack of a restriction inpyproject.toml
or inpoetry.lock
.I prefer to keep
pyproject.toml
the way it is, so it will be possible to runpoetry update
to update all dependencies to their latest versions anytime.