Isotropix Forums

Hi,

About VSCode extention, this is true, that not working. I will take a look at home when I have time.

About the import ix_helper working in Clarisse, this is normal that it doesn't work in Clarisse. The goal of this package it allow you to use Clarisse stuff outside of Clarisse. If you take a look to the content of ix_helper.py the ix.api is injected inside of this python file.
Inside of Clarisse you have to use the standard ix module that is already loaded.

Regards

bvaldes wrote:About VSCode extention, this is true, that not working. I will take a look at home when I have time.

Ok, I'll look forward to it

About the import ix_helper working in Clarisse, this is normal that it doesn't work in Clarisse. The goal of this package it allow you to use Clarisse stuff outside of Clarisse. If you take a look to the content of ix_helper.py the ix.api is injected inside of this python file.
Inside of Clarisse you have to use the standard ix module that is already loaded.

Hmm..then it is not useful as of course the code I write in VSCode must work inside Clarisse
Is there any import combination that gives the linter ok result and still works in Clarisse?
You said you use VSCode for Clarisse code as well, so you don't use linting then?

Antti

Hi,

To make a generic import that work both in VSCode and in Clarisse you can do something like that:

python code

import sys
if not "ix" in sys.modules:
    import ix_helper
    ix = ix_helper.ix

About VSCode and the auto-completion, I don't use it for Clarisse. Most of time the functions are not written in python so the arguments are *args that is not really helpful. So the only thing that can auto-completion do is to purpose you a function but you don't know how to use it because there is no doc neither arguments. Most of time I am searching in the documentation and I am using the Clarisse auto-completion to look for a function and get what is needed in the documentation. VSCode is my default IDE so I write code faster with it than with Clarisse's one, even without completion.

Keep in mind that you are using a module that is not really supposed to be standalone so the linter won't help you that much except to fix wrong variable/functions name. I agree with you that could be very nice if VSCode would have complete intellisense for Clarisse but it's not even possible for Clarisse right now so it will be more difficult to have it for VSCode.

I hope this will help you.

Beat regards

Thank you, that solves all other linter errors except ix.api is still not found
Where the api is actually defined and how it is made to be ix.api?

Hi,

It's defined in the ix_helper module. But with a weird way to do that the linter doesn't understand. You can if you want create your own ix_helper module to fix the issue.

Regards