Error: cannot import name 'cli' from 'interpreter'

[killianlucas]

Error: cannot import name 'cli' from 'interpreter'

[KillianLucas]

This is a weird one. We have an unconventional setup with the CLI to keep things simple for Python users:

When the user starts the CLI, poetry will run interpreter.cli().
interpreter is an instance of the Interpreter class in interpreter.py, which has a method called cli.

What's nice about having the instance as the module, is that when Python users run import interpreter they get an instance of interpreter, which is way more intuitive to me.

But this means we risk circular imports and other weird stuff like this.

ChatGPT is telling me that some systems import things in different orders, and this could be causing the problem.

Let me get back to you on this one. Thanks for opening an issue @antondkv.

[uthpala1000]

same on windows

[uthpala1000]

This is a weird one. We have an unconventional setup with the CLI to keep things simple for Python users:

When the user starts the CLI, poetry will run interpreter.cli(). interpreter is an instance of the Interpreter class in interpreter.py, which has a method called cli.

What's nice about having the instance as the module, is that when Python users run import interpreter they get an instance of interpreter, which is way more intuitive to me.

But this means we risk circular imports and other weird stuff like this.

ChatGPT is telling me that some systems import things in different orders, and this could be causing the problem.

Let me get back to you on this one. Thanks for opening an issue @antondkv.

I managed solve it just by removing the dot . from .cli to from cli

[uthpala1000]

I managed solve it just by removing the dot . from .cli to from cli

remove dot from interpreter.py . from .cli to from cli

[KillianLucas]

Thanks @uthpala1000 and @antondkv. This is so weird, it's the opposite for me (breaks if I remove the dot). Is there any precedent for doing something like this?

try:
  from .cli import cli
except:
  from cli import cli

Have either of you seen something like this before / know what's going on?

[antondkv]

@KillianLucas, thank you for the reply! I have already re-installed the module using the Python --user ENV instead of the root one, and this problem has disappeared for me