[Distutils] pipenv best practices?

[Chris Withers]

Hi All,

Couldn't find an obviously better discussion forum than this for pipenv 
stuff, but please point me to where the rest of the discussions are 
happening...

So, with pipenv, what files do we version control for a project? both 
Pipfile and Pipfile.lock?
Hopefully one I missed from the docs: with the correct files source 
controlled, how do I reproduce the environment on another machine?

Continuing on the deployment theme: I'm used to being able to put 
/path/to/some/ve/bin/some_script in crontabs and the like, where 
some_script comes form a setuptools entry point.
What's the canonical way of doing this with pipenv?

Last up, how should pipenv be used for library development? (ie: where 
dependencies and minimal constraints are expressed in setup.py and where 
you want to test against as many python versions and library 
combinations as you support).

Other than sadness around capitalisation of the config file names, it 
looks really exciting :-)

cheers,

Chris