How to use pipenv + developing?

My typical workflow involves installing my package with pip’s editable mode, i.e.

/path/to/my/project$ pip install -e .

Which is how I get my dependencies - from my setup.py install_requires section. Mainly because I have console scripts setup.

Is this orthogonal to pipenv, or is there any (planned) support for this type of workflow?

[waynew]

Ah-hah! I figured out how to do what I was expecting:

pipenv install $(pip freeze | grep -v git)

You’d have to replace git with whatever VCS you’re using for your editable packages, but I guess this command probably does a better way of explaining the feature that I was expecting to be available.

Presumably from there there’s a nice way to gather the requirements from the Pipfile into setup.py? Or is that something in the works by the distutils team?

[kennethreitz]

currently you would do the following:

$ pipenv shell
$ pip -e .