Freezing Python’s Dependency Hell
What's wrong with pipenv? I am genuinely curious.On local :    mkdir my_project_directory
    cd my_project_directory
    export PIPENV_VENV_IN_PROJECT=1 (To make the virtual environment folder determininstic(.venv/) otherwise you will get a hash based directory(my_project_directory-some-hash-value) which might not be suitable for automatic deployments in applications like docker. I don't know why this is not default.)
    pipenv --python 3.6 (or any particular version number)
    pipenv install numpy scipy pandas matplotlib requests
    pipenv graph (Gives me a dependency graph)
    git add .
    git commit -a -S -m "init" 
    git push

On remote :    git clone url/my_project_directory
    cd my_project_directory
    export PIPENV_VENV_IN_PROJECT=1
    pipenv install
    pipenv shell
    pipenv graph


Is this workflow not enough? I have recently started using pipenv after a lot of struggle. The only issue I have is, Pycharm doesn't allow native pipenv initialisation. I always end up creating an environment manually and then importing the project. Pycharm does detect the environment though.