From 81a0141771cfcec1af47d7a9b0938271a6ce2d58 Mon Sep 17 00:00:00 2001 From: Samuel Ainsworth Date: Mon, 10 Jan 2022 17:31:03 -0800 Subject: [PATCH] Fix file path for file generated during the build process The built file is now `Pkg.dir("PyCall","deps","deps.jl")` as discovered in the investigation of https://github.com/JuliaPy/PyCall.jl/issues/952. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d05ee329..9e9f65fb 100644 --- a/README.md +++ b/README.md @@ -78,7 +78,7 @@ directly to the `libpython` library. But it finds the location of Subsequent builds of PyCall (e.g. when you update the package via `Pkg.update`) will use the same Python executable name by default, unless you set the `PYTHON` environment variable or delete the file -`Pkg.dir("PyCall","deps","PYTHON")`. +`Pkg.dir("PyCall","deps","deps.jl")`. **Note:** If you use Python [virtualenvs](https://docs.python-guide.org/en/latest/dev/virtualenvs/),