Error ocurred while updating

Rated 3.81/5 based on 812 customer reviews

If Spyder does not start at all and before submitting a bug report, please try to reset settings to defaults by running Spyder with the command line option '--reset': this command will remove all your Spyder configuration files located in 'C:\Users\praveen.spyder-py3').

If Spyder still fails to launch, you should consult our comprehensive Troubleshooting Guide, which when followed carefully solves the vast majority of crashes; also, take the time to search for known bugs or discussions matching your situation before submitting a report to our issue tracker. Tried 'spyder --reset' but no use, it still crashed.

Importing it, I got a number of warnings, but everything worked: WARNING (theano.configdefaults): g not available, if using conda: `conda install m2w64-toolchain` C:\Anaconda3\envs\theano-test\lib\site-packages\theano\ User Warning: Deprecation Warning: there is no c compiler.

This is deprecated and with Theano 0.11 a c compiler will be mandatory warnings.warn("Deprecation Warning: there is no c compiler." WARNING (theano.configdefaults): g not detected !

After installing the basic packages, the kernel started fine and I could run simple commands.

This was unchanged after installing Theano, and I didn't get any compilation or install errors building the package and all the messages indicated success.

thanks @steff456 and @dalthviz, this is the error I was telling you about.

Assuming it doesn't, please describe in detail how you installed Keras and any other related packages (with just Thanks for your detailed response, @CAM-Gerlach.

Yes, I confirm that I got the below error as shown by you: An error ocurred while starting the kernel: b'' I have not switched any options in spyder.

According to @nadianaji's report and the Stack Overflow question I referenced above, it seems related to Tensorflow, Keras or Theano.

@ccordoba12 Sure, I can try to repro it by that method after I get an environment set up, but if you're after the cause of the message in general rather than a particular manifestation of it (I'm not sure its actually one specific error, but a symptom of various potentially different lower-level problems), I have at least one semi-consistent way to trigger it, as I have encountered this error message before on other issues.

Leave a Reply