Skip to content

"source deactivate" does not work inside the environment once it has been activated with your script on MacOSX #7

@sebma

Description

@sebma

Hi,

First, let me congratulate you for this great tool 👍

I'm using MacOSX 10.12 at work and once I cd /path/to/my/python2/only/environment
and try to import numpywhich is not installed so these lines below behave as I expected :

/path/to/my/python2/only/environment : $ python -c "import numpy"
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named numpy

If I want to come back to my original environment (where numpy is already installed) with source deactivate I still get the same error :

/path/to/my/python2/only/environment : $ source deactivate
/path/to/my/python2/only/environment : $ python -c "import numpy"
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named numpy

If I cd .. or just cd and then type source deactivate, then the $ python -c "import numpy" works fine.

Can you have a look ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions