cleo library has built-in support for terminal colors, and already defines semantic styles, s.a, info, comment, question and error.

Using self.line and self.line_error style argument we can drop the dependency on simple-chalk library, as it is only being used to display error messages in red, and info messages in dim.

Tested locally by pulling the plugin with poetry self add https://github.com/ajcerejeira/poetry-exec-plugin.git.

Here is how an info message is rendered under Gnome terminal:

And this is how an error message looks like:

Hi, thanks for this utility, looks promising! I've found a bug that stucks me sometimes, so I've decided to submit a patch.

If you create a command like:

[tool.poetry-exec-plugin.commands]
printf = "printf"

You can't pass it strings with spaces because the words after the space are not properly passed to the command:

$ poetry exec printf -- 'Hello world\n'
Exec: printf Hello world\n

Hello<my-user>@<myenv>

This turns many commands unusable. For example is not possible to execute a pytest test that have spaces in their id:

[tool.poetry-exec-plugin.commands]
test = "pytest"

[tool.poetry-exec-plugin.commands]
$ poetry exec test -- -svv 'tests/path/to/test.py::test_name[my id]'
Exec: poetry exec test -- -svv 'tests/path/to/test.py::test_name[my id]'
===== test session starts =====
platform linux -- Python 3.7.13, pytest-7.1.2, pluggy-1.0.0 -- /my/python
cachedir: .pytest_cache
rootdir: ..., configfile: pyproject.toml
plugins: cov-3.0.0
collected 0 items                                                                                                                          

===== no tests ran in 0.01s =====
ERROR: file or directory not found: id]

So this fixes it using shlex.join, with a backport for Python3.7 that should be removed when that version reaches their EOL.

I've rewritten the test suite to remove mocks and because cleo.testers.command_tester.CommandTester does not allow to pass arguments to commands.

Bumps certifi from 2022.6.15 to 2022.12.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

For example if I execute poetry exec docs and a doc command exists, instead of showing this error (current):

$ poetry exec docs

Unable to find the command 'docs'. To configure a command you must add it to your pyproject.toml under the path [tool.poetry-exec-plug
in.commands]. For example:

[tool.poetry-exec-plugin.commands]
docs = "echo Hello World"

It would show something like:

$ poetry exec docs

Unable to find the command 'docs'. Perhaps you wanted to run the 'doc' command?

$ npm run docs
npm ERR! Missing script: "docs"
npm ERR! 
npm ERR! Did you mean one of these?
npm ERR!     npm run doc
npm ERR!     npm run doc:show
npm ERR! 
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

Really cool and promising plugin!

Is it possible to specify the plugin installation from the project's pyproject.toml file?

That way, we wouldn't have to specify the plugin as a requirement in our CI builders and dev-machine setup, and simply be allowed to do (whether or not the plugin is installed) :

poetry install
poetry run test

Thanks!