New tool lets you pull detailed Claude Code transcripts by tapping a reverse‑engineered private API. Run it with a single uvx command, output as clean HTML or a Gist. Inspired by Simon Willison’s demo, it brings command‑line magic to AI code reviews. Give it a try! #ClaudeCode #ReverseEngineeredAPI #uvx #CommandLine
🔗 https://aidailypost.com/news/tool-extracts-detailed-claude-code-transcripts-via-reverseengineered
Similar to my `uvx add-classifiers` and `uvx add-link` mini projects, recently made a `uvx set-license` to simplify that step of setting up new projects.
https://pypi.org/project/set-license/
https://codeberg.org/kfdm/set-license
Light wrapper around https://api.github.com/licenses to add the `license` line to `pyproject.toml` and write to `LICENSE.md`
#python #uvx #pipx
uvx 與 PEP 723 的組合
最近 Hacker News 上蠻多 uv 相關的條目,看到「Fun with uv and PEP 723」這篇 (via),透過 uvx 與 PEP 723 組出接近 standalone script 的環境。 一般的 Python script 通常都會需要一個環境 (像是 venv) 把相依性套件都裝起來,而相依性一般都是放在另外一個檔案裡面 (像是 requirements.txt 或是 pyproject.
Gea-Suan Lin's BLOG#uv and #uvx are great tools, but they modifies and sometimes break #python executables if those contain "from __future__" imports. This also affected #bottlepy, but there is a workaround: https://github.com/astral-sh/uv/issues/6489#issuecomment-2973748865
You can now use bottle with uvx again (e.g. `uvx bottle --help`)

Scripts that use "from future" can result in syntax error when used with uvx · Issue #6489 · astral-sh/uv
When using uvx with script files that have from future import and shebang with a space, I receive the following syntax error: from __future__ import print_function, unicode_literals ^^^^^^^^^^^^^^^...
GitHub