Ytukyg

I was trying to install Keras on my python 3.7 environment then I noticed that neither tensorflow nor keras supports python 3.7, they support 3.6

Then I created a new virtual environment with python 3.6 using conda/anaconda.

I was able to activate this virtual environment by entering
activate deeplearning in the cmd and then type python to enter python shell.
I installed Keras and its dependencies using conda install -c conda-forge keras , it seemed okay I entered the python shell imported keras and other libraries tinkered around with the libraries, they were working as intended.

I closed down the window to try again if i can open up the virtual environment again manually myself.
Typed activate deeplearning, and then I ran into this problem(
Screenshot
)
I only typed the activate deeplearning part on the cmd screenshot.


The problem here is that I can not enter the virtual environment, I get this commands? on the cmd and then it shuts itself down. I can not enter the virtual environment therefore preventing me from installing new libraries. But I can enter the python shell of this environment from where it is installed.
However there is not a .bat file in the folder so I can not activate the virtual environment from there as well.


I do not know what to do, I would really appreciate it if someone could help, thanks in advance.

It seems that the scripts for activating keras are exiting prematurely. One of the reasons can be that the environment is not set in python 3.6.

Try creating a virtual environment with command:

conda create --name deeplearning python=3.6

And then you can follow instructions from:
http://inmachineswetrust.com/posts/deep-learning-setup/

Note: While installing keras use command:

conda install keras

I fixed this on Python 2.7 by removing via Anaconda Navigator the item that goes by the name vs2008_win-32, that fixed my environment.

On my system, the error was caused by another activation script, probably installed at the same time. To confirm that this is the case for you, look into the batch file generated dynamically at startup. To find out its name, change _conda_activate.bat as so:

...



:FIXUP43

@FOR /F "delims=" %%i IN ('@CALL "%CONDA_EXE%" shell.cmd.exe %*') DO @SET "_TEMP_SCRIPT_PATH=%%i"

@IF "%_TEMP_SCRIPT_PATH%"=="" @EXIT /B 1

@IF NOT "%CONDA_PROMPT_MODIFIER%" == "" @CALL SET "PROMPT=%%PROMPT:%CONDA_PROMPT_MODIFIER%=%_empty_not_set_%%%"



:: Add these lines:

set _TEMP_SCRIPT_PATH

pause



@CALL "%_TEMP_SCRIPT_PATH%"

...

In the temp script comment out the invocation of other scripts
until you find the culprit. For me it was something to do with vs2015.

@SET "PYTHONIOENCODING=1252"

@CALL "C:Usersx030551AppDataLocalContinuumminiconda3etccondaactivate.dkeras_activate.bat"

:: @CALL "C:Usersx030551AppDataLocalContinuumminiconda3etccondaactivate.dvs2015_compiler_vars.bat"

Once I had this information, Google pointed me to this issue. The solution to that depends too much on your environment to post here.