This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
dmenv tidy does not work from inside a virtualenv #110
Comments
dmerejkowsky
added a commit
that referenced
this issue
Nov 2, 2019
dmerejkowsky
added a commit
that referenced
this issue
Nov 6, 2019
Goal: get rid of the Project struct altogether and fix #110 properly. First step: * Extract a Context struct to hold paths, venv_runner and python_info This commit does that for the `install` and `process_scripts` methods
dmerejkowsky
added a commit
that referenced
this issue
Nov 6, 2019
dmerejkowsky
added a commit
that referenced
this issue
Nov 6, 2019
Goal: get rid of the Project struct altogether and fix #110 properly. This commit implements the first step by extracting a Context struct to hold paths, venv_runner and python_info
dmerejkowsky
added a commit
that referenced
this issue
Nov 6, 2019
dmerejkowsky
added a commit
that referenced
this issue
Nov 6, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here's what happens:
The problem is that we read PythonInfo only once, and that info becomes obsolete between the clean and the virtualenv recreation...
The text was updated successfully, but these errors were encountered: