Skip to content

Docs: Clarify global command usage in README#2

Open
Gitreceiver wants to merge 1 commit intomainfrom
docs/clarify-global-usage
Open

Docs: Clarify global command usage in README#2
Gitreceiver wants to merge 1 commit intomainfrom
docs/clarify-global-usage

Conversation

@Gitreceiver
Copy link
Copy Markdown
Owner

The tama command is made globally accessible within its virtual environment through the [project.scripts] configuration in pyproject.toml. This was already correctly set up.

This commit updates the README.md to:

  • Explicitly state that tama becomes globally available after installation within the activated virtual environment.
  • Add a troubleshooting section for you if you encounter issues with accessing the command, covering common scenarios like inactive virtual environments or PATH issues.

The `tama` command is made globally accessible within its virtual
environment through the `[project.scripts]` configuration in
`pyproject.toml`. This was already correctly set up.

This commit updates the README.md to:
- Explicitly state that `tama` becomes globally available after installation within the activated virtual environment.
- Add a troubleshooting section for you if you encounter issues with accessing the command, covering common scenarios like inactive virtual environments or PATH issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant