Using "run" with no arguments gives unclear error message

[noa-weiss]

• I am on the latest Poetry version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• WSL-2 on Windows 11

• Poetry version 1.1.12

Issue

Using "poetry run" without arguments gives the following error message:

FileNotFoundError

  [Errno 2] No such file or directory: b'/snap/bin/run'

  at /usr/lib/python3.8/os.py:601 in _execvpe
       597│         path_list = map(fsencode, path_list)
       598│     for dir in path_list:
       599│         fullname = path.join(dir, file)
       600│         try:
    →  601│             exec_func(fullname, *argrest)
       602│         except (FileNotFoundError, NotADirectoryError) as e:
       603│             last_exc = e
       604│         except OSError as e:
       605│             last_exc = e

It would be better, and much clearer, to have an error message that informs the user the command is failing due to missing arguments.

[branchvincent]

Thanks for filing! This has been fixed on master and will be released with the upcoming 1.2:

$ poetry --version
Poetry (version 1.2.0a2)
$ poetry run

Not enough arguments (missing: "args")

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.