@truskovskiyk @RohitSaha

I would also make llmtune as the entry point for running the CLI. Instead of doing python toolkit.py --config-path config.yaml, users can just do llmtune --config-path config.yaml. We can also add a pipx installation instruction so CLI lives in an isolated virtual environment.

I have made the following changes in my local machine and can verify it works.

1. Move toolkit.py into llmtune/cli/tookit.py
2. Modify the entrypoint in toolkit.py

- if __name__ == "__main__":
-     app()

+ def cli():
+     app()

4. Add script entry point in pyproject.toml

+ [tool.poetry.scripts]
+ llmtune = "llmtune.cli.toolkit:cli"

Related: #108

Looks good! Please take a look at comment #115.

Also, any reason of using twine vs poetry publish?

agree, poetry publish is much better, updated

@truskovskiyk @RohitSaha

I would also make llmtune as the entry point for running the CLI. Instead of doing python toolkit.py --config-path config.yaml, users can just do llmtune --config-path config.yaml. We can also add a pipx installation instruction so CLI lives in an isolated virtual environment.

I have made the following changes in my local machine and can verify it works.

1. Move toolkit.py into llmtune/cli/tookit.py
2. Modify the entrypoint in toolkit.py

- if __name__ == "__main__":
-     app()

+ def cli():
+     app()

4. Add script entry point in pyproject.toml

+ [tool.poetry.scripts]
+ llmtune = "llmtune.cli.toolkit:cli"

good idea, please create issue