INFORMATION ONLY: Config PyCharm to run LPython

[rebcabin]

in the directory lpython/src/bin, create a symbolic link from lpython to python

ln -s lpython python

In PyCharm, create a new project and set up its interpreter to be that lpython/src/bin:

ignore all the warnings and errors.

It starts to work!

[rebcabin]

[rebcabin]

I have not succeeded in configuring CLion from JetBrains to build LPython, yet, but will give it another try in a few days.

[rebcabin]

can make red-underlines go away by adding lpython/src/runtime/lpython to PYTHONPATH in the PyCharm GUI:

[rebcabin]

Using PyCharm to run LPython is a big boost (fewer keystrokes!)

I don't miss debugger integration because pudb is REALLY good at the terminal. Using pudb to debug LPython is a HUGE PLUS to our original decision that LPython IS CPython -- you can always run valid LPython code in CPython!

PYTHONPATH='../../src/runtime/lpython' python -m pudb lasr_lexer.py  

[certik]

Very good. We need a solid editor integration -- we can print the error messages in other formats (LFortran supports JSON as well) so that editors can take it and shows the errors in the source code.

We can also do a Language Server. We did some preliminary work last summer.

[rebcabin]

NOTE: The symbolic link causes integration tests to Falsely Fail :) (false negatives). Just change the name of the symbolic link before running the integration tests, then change it back. See closed Issue #1980.