"ek.set_app_key" in Python Spyder

I assume the log file output is for when you run in Spyder? If so, the line Set App Key: None is troubling as this would indicate you are not providing an AppKey?

Your Anaconda screenshot confirms that from Anaconda prompt you are able to connect to Eikon and get a valid response. The key line is Port 9000 on local proxy was detected - which indicates a successful connection.

I have also spoken with the Eikon Data API development team and they can confirm they have never faced any issues when testing with Spyder.

This would seem to narrow this down to an issue with your particular Spyder installation. As Spyder is a 3rd party application the only suggestions I can offer are to try and uninstall and re-install Spyder to see if that helps.

Alternatively, you could use Spyder IDE as your editor to create/edit your script and then run the script from the Anaconda prompt - instead of from within Spyder. I appreciate this is not ideal - but this is a workaround I would consider using as a developer if I could not figure out what was wrong with my IDE.

Failing that there are other IDEs available such as Visual Studio Code.

All comments

Please advise what you mean by does not work?

Do you see any error message / other output?

Please try enabling logging to see if that provides any relevant information e.g.

import logging.config 
ek.set_log_level(logging.DEBUG) 
ek.set_app_key('<your app key>')

Just to confirm that I did try a quick test in Spyder and it worked fine.

Also, can you confirm what happens if you run a basic script with set_app_key in a Python console?

Hi Umer thank you for the reply. Here is a screenshot. After running the command ek.set_app_key('my api key') everything just froze.

Thanks for the update.

And can you confirm what happens when you run the script in a standalone console outside of Spyder? e.g. at the Anaconda prompt and a standard Python console invoked directly from Windows (rather than from within Spyder)?

for example:

Also, please confirm the version of eikon library installed

import eikon as ek
ek.__version__

You should also have a Log file generated in the working directory e.g. something like pyeikon.20200424.10-47-44.log - please remove any AppKey etc from the log file before attaching to your reply.

One final thing, have you tried completely shutting down the Eikon application instance and restarting it - we have had the odd occasion where the Eikon library refuses to connect and a restart fixes it. Note that exiting Eikon does not necessarily shut it down - you may have to use the little icons in the bottom left to shut it down completely.

moragodkrit.chumsri_1

@toddc1021

I can run the latest version of eikon data API 1.1.2 with spyder.

I'm using spyder 4.1.2. Not sure do you have any virus scan or firewall that detecting some behavior and causes it hangs?

Thank you Umer.

In Spyder when I type ek.__version__ it tells me '1.1.2'.

I am using Spyder 4.1.2.

Yes I have tried shutting down Eikon and restarting it.

Could you please guide me through "when you run the script in a standalone console outside of Spyder? "

I opened Anaconda prompt as an administrator and tried to type in the command but it doesnt seem to work. A screenshot is attached. Would appreciate if you could provide more detailed steps. Thank you very much.

Thank you Moragodkrit. I am running eikon data api 1.1.2 with Spyder 4.1.2. I, not sure if it has to do with any virus scan but this situation has never occurred when I am using other python packages.

I have written it in my first post but just to make sure its clear: I have no problem using eikon api in jupyter notebook. The problem only occurs in spyder.

moragodkrit.chumsri_1

@toddc1021

I mentioned the antivirus or firewall because Eikon Data API has to open an internal communication port to Eikon Desktop. I found a similar issue with spyder last year with another library, and it hangs/freezes like this. Seems like some firewall app in my PC try to block the behavior. I tried to disable windows defender/firewall/antivirus, and it seems to resolve. When I enable it again, the problem seems to disappear. So I don't know what they did.