if a version constraint changes in the Pipfile, the pyproject.toml does not reflect the change

A requirement of celery[redis] = '*' should create a entries like this:

celery = {extras = ["redis"], version = "^4.4.7"}

I don't know how pipenv does it's work, but I guess poetry itself can generate the entries for correctness?

Thanks for the tool!

This tool has a wrong transformation for dependency like that

pipenv-poetry-migrate = {editable = true,git = "https://github.com/yhino/pipenv-poetry-migrate.git",ref = "master"}

when have multiple sources, it's generating

package = {version = "*", index = "private_index"}

instead of:

package = {version = "*", source = "private_index"}

Implemented it at #24, but since it is not documented, no one knows that it can be used.

The python-semantic-release configuration has changed.
The commands have also changed, so the release flow needs to be adjusted.

ref. https://python-semantic-release.readthedocs.io/en/latest/index.html

If pyproject.toml does not exist yet then there should be a message that suggests running poetry init.

pipenv-poetry-migrate 0.1.3 requires tomlkit<0.6.0,>=0.5.11, but you'll have tomlkit 0.7.0 which is incompatible.

What should we do?

https://python-poetry.org/docs/master/managing-dependencies/#dependency-groups

Poetry will slowly transition away from the dev-dependencies notation which will soon be deprecated, so it’s advised to migrate your existing development dependencies to the new group notation.

Allow notation selection and migration with arguments.