From c9fd0a99c8269ac6fc3218d304449bb03f157afb Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Sat, 22 Jun 2019 17:51:48 +0200 Subject: [PATCH] Clarify Pipfile's use of relative paths --- repo2docker/buildpacks/pipfile/__init__.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/repo2docker/buildpacks/pipfile/__init__.py b/repo2docker/buildpacks/pipfile/__init__.py index 3e291668..060f5ed6 100644 --- a/repo2docker/buildpacks/pipfile/__init__.py +++ b/repo2docker/buildpacks/pipfile/__init__.py @@ -96,6 +96,9 @@ class PipfileBuildPack(CondaBuildPack): python = "${KERNEL_PYTHON_PREFIX}/bin/python" pipfile = self.binder_path("Pipfile") pipfile_lock = self.binder_path("Pipfile.lock") + # let pipenv work relative to the dir that has the Pipfile that can + # contain relative references such as: + # my_package = {path=".", editable=true} working_directory = self.binder_dir or "." assemble_scripts.append(("${NB_USER}", "pip install pipenv")) # if Pipfile.lock isn't found, Pipfile is used to create one