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
As the title expresses trying to activate a conda environment either in the command line or in, say a VisualCode environment causes an import collision.
For example in: nupic.research/projects/location_layer/single_layer_2d_experiment
The current workaround is to activate the environment in the parent directory.
A better solution would be to rename the project specific logging.py modules to say experiment_logging.py
The text was updated successfully, but these errors were encountered:
fcr
changed the title
Local lo
Local logging.py modules prevents activating Conda environments in the projects that have this module
Jun 9, 2024
As the title expresses trying to activate a conda environment either in the command line or in, say a VisualCode environment causes an import collision.
For example in:
nupic.research/projects/location_layer/single_layer_2d_experiment
The current workaround is to activate the environment in the parent directory.
A better solution would be to rename the project specific logging.py modules to say experiment_logging.py
The text was updated successfully, but these errors were encountered: