How to stop poetry from CLI intercepting options for a command registered by a plugin?

[nat-n]

I have a poetry plugin that registers a command

When I run the following command I poetry intercepts the --version option and prints version details instead of executing the command.

poetry poe --version

What I want instead is for poetry to invoke the command and let it handle the option. I'm lead to believe that this is possible, because it works as expected for the run command, e.g.

poetry run poe --version

However I can't spot anything about the implementation of the run command that makes it special. Is there any way to achieve the same thing with another command added via the CommandLoader in a plugin?

[abn]

Hey @nat-n !

The run command is a snow-flake unfortunately. See

poetry/src/poetry/console/application.py

Line 416 in 79c207b

def _configure_run_command(self, io: IO) -> None:

for handling logic.

Also, it is inadvisable to reuse global options. They will always be processed first. See

poetry/src/poetry/console/application.py

Line 356 in 79c207b

def _sort_global_options(self, io: IO) -> None:

.

[abn]

In your case, you could suggest something like this.

poetry run -- poe --version

Kind of beats the purpose I think.

[nat-n]

Thanks for clarifying 👍