Clarify how Jedi autocompletes about jedi HOT 2 CLOSED

As long as you write pure python, everything is done statically. But: If you use builtin modules (c_builtin) there is no other option than to execute those modules. However: Execute isn't that critical (as e.g. in pythoncomplete), because it means one import and no more. After this import a Python file will be generated that contains all the definitions of a builtin module.

So basically the only dangerous thing is using the import itself. If your c_builtin uses some strange initializations, it might be dangerous. But if it does you're screwed anyways, because at one moment you're going to execute your code, which executes the import.

Is this enough? I would add it to the documentation, later on.

from jedi.

Wonderful. That sounds great to me and I think it would be a good addition
to the docs whenever you add it.

Thanks again!

On Monday, October 22, 2012, David Halter wrote:

As long as you write pure python, everything is done statically. But: If
you use builtin modules (c_builtin) there is no other option than to
execute those modules. However: Execute isn't that critical (as e.g. in
pythoncomplete), because it means one import and no more. After this import
a Python file will be generated that contains all the definitions of a
builtin module.

So basically the only dangerous thing is using the import itself. If your
c_builtin uses some strange initializations, it might be dangerous. But if
it does you're screwed anyways, because at one moment you're going to
execute your code, which executes the import.

Is this enough? I would add it to the documentation, later on.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-9656172.

from jedi.