pyproject-pipenv 1.1.1

Sync requirements from Pipfile to pyproject.toml

pyproject-pipenv

Sync properties from Pipfile to pyproject.toml.

Never need again to change dependencies manually in pyproject.toml (or forget to do it and publish a broken package), and enjoy the same dependency locking or semantic versioning.

Also allows just checking to be used as part of CI lint/format steps.

Install

# in your project virtualenv (or globally / pipx)
$ pip install pyproject-pipenv
...

Usage

Check:

$ pyproject-pipenv
Dependencies out of sync:
- tomlkit<2.0.0
+ tomlkit<1.0.0
pyproject.toml NEEDS UPDATE!

Apply:

$ pyproject-pipenv --fix
Dependencies out of sync:
- tomlkit<2.0.0
+ tomlkit<1.0.0
pyproject.toml UPDATED!

Features

• Syncs
  • Dependencies
  • Python version required

ToDo

• Handle markers and all that extra crap besides version
• Sync more fields

Context

For some reason, neither pyproject nor pipenv interact with each other:

• You use pipenv (and Pipfile) while developing, because it's great
• You add all the package details to pyproject.toml
• You work on the code and add new dependencies
• Then you publish the new version only to notice you forgot to add the dependencies also to pyproject dependencies entry...

dephell seemed to be a solution but it is dead. Forking it sounds too much, as it supports many different things than I need.

pipenv-setup seems to be the same but for setup.py instead of pyproject.toml. Probably a good source for inspiration after this initial version.