You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated to direnv v2.13.0 and I see un expected behavior. I have a tree of directories with nested environments that source the top level using source_up. In the highest level I have a custom Python virtualenv defined by using layout python python2.7. In the children I would have custom settings but I would not define a new layout for python.
Up to direnv v2.12.2 the way it worked is that if I moved into a child directory a Python virtualenv would be configured by the parent .envrc within a .direnv directory within the parent. All the children would share the same version of Python.
When I upgraded to direnv v2.13.0, now every time I move into a child directory, a new version of the virtualenv is created within a .direnv directory in the children directories, instead of reusing the parent .direnv.
Is this a bug or a change in behavior?
The text was updated successfully, but these errors were encountered:
I just updated to direnv v2.13.0 and I see un expected behavior. I have a tree of directories with nested environments that source the top level using
source_up
. In the highest level I have a custom Python virtualenv defined by usinglayout python python2.7
. In the children I would have custom settings but I would not define a new layout for python.Up to direnv v2.12.2 the way it worked is that if I moved into a child directory a Python virtualenv would be configured by the parent
.envrc
within a.direnv
directory within the parent. All the children would share the same version of Python.When I upgraded to direnv v2.13.0, now every time I move into a child directory, a new version of the virtualenv is created within a
.direnv
directory in the children directories, instead of reusing the parent.direnv
.Is this a bug or a change in behavior?
The text was updated successfully, but these errors were encountered: