-
uv init -
Do not do
uv sync -
pyproject.tomlis the backbone of this entire pkg:- change name (by default it takes the root directory name)
- add description
- in future when we make updates, we change the version here
-
now do
uv sync -
add dependencies:
uv add fastmcp
-
Whenever we create we create a
srcfolder in the root.- in this
srcfolder, we create__init__.pywhich signifiessrcis a pkg not a normal folder.
- in this
-
Ideally the folder (inside
src) containing the pkg logic should be named same as pkg-name written inpyproject.tomlname field. This folder should also contain__init__.pyfile. -
Following commands should be added to
pyproject.tomlto make the pkg work seamlessly:- Build commands
[build-system] requires = ["setuptools>=42", "wheel"] build-backend = "setuptools.build_meta"- Locating folder for the pkg
[tool.setuptools.packages.find] where = ["src"]- Which file to run when pkg is called
[projecct.scripts] agentic_terminal = "agentic_terminal.main:main" -
After all of the above is done:
uv build(creates.whland.tarfiles indistfolder) -
if we do not wish to deploy, we can share the
.whlfile. -
to test it now locally, we can do
uv pip install whl_file_pathto install theagentic_terminalin our venv and use it as a library. -
add pypi token as env variable in terminal:
$env:UV_PUBLISH_TOKEN="token"thenuv publish
Metadata
Release files for agentic_terminal_rss 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentic_terminal_rss-0.1.0.tar.gz | 2.9 kB | Without provenance | Details for agentic_terminal_rss-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentic_terminal_rss-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agentic_terminal_rss-0.1.0-py3-none-any.whl |
Total release size: 6.3 kB
Release files / agentic_terminal_rss-0.1.0.tar.gz
| Download URL | agentic_terminal_rss-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fcaab0ae69b02d81b76aa166a2b09f36e28875b4366a7d1a048c6a573c63e02
|
|
BLAKE2b-256 checksum How to use checksums |
e94ffb716faed7fb5e6ce2bc84ef5be453a28858d9717877da9f4e3acf084746
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / agentic_terminal_rss-0.1.0-py3-none-any.whl
| Download URL | agentic_terminal_rss-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
740e77e99ab9247d5de92857f003b91558086cbf828a117227091d3ef2d56306
|
|
BLAKE2b-256 checksum How to use checksums |
a0f8ab3f41f52736e5a0c4111c24aef666f13d65b1ae1a9a34aef4f3fb48e1e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for agentic_terminal_rss 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.