Migrating scripts from eikon to lseg.data python module

Am looking to use my eikon Python scripts with Workspace now active, and am aware the Eikon API proxy will no longer be working from July onwards. Is there a way to ensure my scripts remain compatible after July?

Related question - does just opening an ld.open_session() accomplish the same thing in Workspace as ek.set_app_key did for Eikon?

Find more posts tagged with

eikon

migration

lseg-data

Accepted answers

All comments

Gurpreet

Hello @sid_ghoshal

The new LD Library is quite similar to the EDAPI. Your code should be able to work with some minimal changes. I would recommend to try the library samples now and ask away any technical question on this forum.

Opening the session on the LD Library is same as setting the AppKey in EDAPI.

Jirapongse

@sid_ghoshal

The LSEG Data Library for Python has a configuration file (lseg-data.config.json). You can specify an application key in the configuration file.

        "desktop": {

            "workspace": {

                "app-key": "YOUR APP KEY GOES HERE!"

            }

        }

Then, set the default session to "desktop.workspace".

    "sessions": {

        "default": "desktop.workspace",

In the code, you can call the ld.open_session() to open the default session.

Otherwise, you can specify an application key while calling the ld.open_session().

 ld.open_session(app_key = "APP KEK")

For more information, please refer to the Essential Guide to the Data Libraries - Generations of Python library (EDAPI, RDP, RD, LD) article.

EXPLORE OUR SITES