{"version":"https:\/\/jsonfeed.org\/version\/1","title":"mathspp.com feed","home_page_url":"https:\/\/mathspp.com\/blog\/tags\/uv","feed_url":"https:\/\/mathspp.com\/blog\/tags\/uv.json","description":"Stay up-to-date with the articles on mathematics and programming that get published to mathspp.com.","author":{"name":"Rodrigo Gir\u00e3o Serr\u00e3o"},"items":[{"title":"TIL #140 \u2013 Install Jupyter with uv","date_published":"2026-03-03T16:16:00+01:00","id":"https:\/\/mathspp.com\/blog\/til\/install-jupyter-with-uv","url":"https:\/\/mathspp.com\/blog\/til\/install-jupyter-with-uv","content_html":"

Today I learned how to install jupyter properly while using uv to manage tools.<\/p>\n\n

Running a Jupyter notebook server or Jupyter lab<\/a><\/h2>\n

To run a Jupyter notebook server with uv, you can run the command<\/p>\n

$ uvx jupyter notebook<\/code><\/pre>\n
Similarly, if you want to run Jupyter lab, you can run<\/p>\n
$ uvx jupyter lab<\/code><\/pre>\n
Both work, but uv will kindly present a message explaining how it's actually doing you a favour, because it guessed<\/em> what you wanted.\nThat's because uvx something<\/code> usually looks for a package named \u201csomething\u201d with a command called \u201csomething\u201d.<\/p>\n
As it turns out, the command jupyter<\/code> comes from the package jupyter-core<\/code>, not from the package jupyter<\/code>.<\/p>\n
Installing Jupyter<\/a><\/h2>\n
If you're running Jupyter notebooks often, you can install the notebook server and Jupyter lab with<\/p>\n
$ uv tool install --with jupyter jupyter-core<\/code><\/pre>\n
Why uv tool install jupyter<\/code> fails<\/a><\/h3>\n
Running uv tool install jupyter<\/code> fails because the package jupyter<\/code> doesn't provide any commands by itself.<\/p>\n
Why uv tool install jupyter-core<\/code> doesn't work<\/a><\/h3>\n
The command uv tool install jupyter-core<\/code> looks like it works because it installs the command jupyter<\/code> correctly.\nHowever, if you use --help<\/code> you can see that you don't have access to the subcommands you need:<\/p>\n
$ uv tool install jupyter-core\n...\nInstalled 3 executables: jupyter, jupyter-migrate, jupyter-troubleshoot\n$ jupyter --help\n...\nAvailable subcommands: book migrate troubleshoot<\/code><\/pre>\n
That's because the subcommands notebook<\/code> and lab<\/code> are from the package jupyter<\/code>.\nThe solution?\nInstall jupyter-core<\/code> with<\/em> the additional dependency jupyter<\/code>, which is what the command uv tool install --with jupyter jupyter-core<\/code> does.<\/p>\n
Other usages of Jupyter<\/a><\/h2>\n
The uv documentation has a page dedicated exclusively to the usage of uv with Jupyter<\/a>, so check it out for other use cases of the uv and Jupyter combo!<\/p>","summary":"Today I learned how to install jupyter properly while using uv to manage tools.","date_modified":"2026-03-03T18:05:58+01:00","tags":["python","programming","uv","productivity"],"image":"\/user\/pages\/02.blog\/04.til\/140.install-jupyter-with-uv\/thumbnail.webp"},{"title":"uv cheatsheet","date_published":"2025-09-06T19:36:00+02:00","id":"https:\/\/mathspp.com\/blog\/uv-cheatsheet","url":"https:\/\/mathspp.com\/blog\/uv-cheatsheet","content_html":"
Cheatsheet with the most common and useful uv commands to manage projects and dependencies, publish projects, manage tools, and more.<\/p>\n\n
This cheatsheet lists the most commonly used commands and should be more than enough for you to get started using uv.\nFor more advanced use cases, check the uv docs<\/a> and its guides.<\/p>\n
\n
Last updated for uv version 0.10.9.<\/p>\n<\/div>\n
Download this cheatsheet<\/a><\/p>\n
Creating projects 🧱<\/a><\/h2>\n
<\/th>\n<\/th>\n<\/tr><\/thead>
uv init<\/code><\/td>\nInitialise a project in the current directory<\/td>\n<\/tr>
uv init myproj<\/code><\/td>\nInitialise a project myproj<\/code> in the directory myproj<\/code>\n<\/td>\n<\/tr>
uv init --app --package ...<\/code><\/td>\nInitialise a packageable app (e.g., CLI, web app, ...)<\/td>\n<\/tr>
uv init --lib --package ...<\/code><\/td>\nInitialise a packageable library (code you import)<\/td>\n<\/tr>
\nuv init --python 3.X ...<\/code>1<\/a><\/sup><\/td>\nUse Python 3.X for your project<\/td>\n<\/tr><\/tbody><\/table>
Managing project dependencies 🧩<\/a><\/h2>\n
<\/th>\n<\/th>\n<\/tr><\/thead>
uv add requests<\/code><\/td>\nAdd requests<\/code> as a dependency<\/td>\n<\/tr>
uv add A B C<\/code><\/td>\nAdd A<\/code>, B<\/code>, and C<\/code> as dependencies<\/td>\n<\/tr>
uv add -r requirements.txt<\/code><\/td>\nAdd dependencies from the file requirements.txt<\/code>\n<\/td>\n<\/tr>
uv add --dev pytest<\/code><\/td>\nAdd pytest<\/code> as a development dependency<\/td>\n<\/tr>
uv run pytest<\/code><\/td>\nRun the pytest executable that is installed in your project<\/td>\n<\/tr>
uv remove requests<\/code><\/td>\nRemove requests<\/code> as a dependency<\/td>\n<\/tr>
uv remove A B C<\/code><\/td>\nRemove A<\/code>, B<\/code>, C<\/code>, and their transitive dependencies<\/td>\n<\/tr>
uv tree<\/code><\/td>\nSee the project dependencies tree<\/td>\n<\/tr>
uv lock --upgrade<\/code><\/td>\nUpgrade the dependencies' versions<\/td>\n<\/tr><\/tbody><\/table>
Project lifecycle management 🔄<\/a><\/h2>\n
<\/th>\n<\/th>\n<\/tr><\/thead>
uv build<\/code><\/td>\nBuild your packageable project<\/td>\n<\/tr>
uv publish<\/code><\/td>\nPublish your packageable project to PyPI<\/td>\n<\/tr>
uv version<\/code><\/td>\nCheck your project version<\/td>\n<\/tr>
uv version --bump major<\/code><\/td>\nBump project major version (e.g., 0.3.2 -> 1.0.0<\/code>)<\/td>\n<\/tr>
uv version --bump minor --bump beta<\/code><\/td>\nBump minor version into a beta (e.g., 1.0.0 -> 1.1.0b1<\/code> or 1.1.0b1 -> 1.1.0b2<\/code>)<\/td>\n<\/tr>
uv version --bump rc<\/code><\/td>\nBump version into release candidate (e.g., 1.1.0b1 -> 1.1.0rc1<\/code> or 1.1.0rc1 -> 1.1.0rc2<\/code>)<\/td>\n<\/tr>
uv version --bump stable<\/code><\/td>\nTurn into a stable version (e.g., 1.1.0rc1 -> 1.1.0<\/code>)<\/td>\n<\/tr><\/tbody><\/table>
Managing tools ⚒️<\/a><\/h2>\n
<\/th>\n<\/th>\n<\/tr><\/thead>
uv tool run pytest<\/code><\/td>\nRun pytest<\/code> in an isolated environment<\/td>\n<\/tr>
uv tool run textual-demo --from textual<\/code><\/td>\nRun the command textual-demo<\/code> from the package textual<\/code>\n<\/td>\n<\/tr>
uvx ...<\/code><\/td>\nAlias for uv tool run ...<\/code>\n<\/td>\n<\/tr>
uv tool install ruff<\/code><\/td>\nInstall ruff<\/code> in an isolated environment but make it globally available<\/td>\n<\/tr>
uv tool install --with dep ...<\/code><\/td>\nInstall the given tool with extra dependencies (e.g., install a tool with<\/em> its plugins)<\/td>\n<\/tr>
uv tool list<\/code><\/td>\nList all tools installed<\/td>\n<\/tr>
uv tool upgrade ruff<\/code><\/td>\nUpgrade the ruff<\/code> tool<\/td>\n<\/tr>
uv tool upgrade --all<\/code><\/td>\nUpgrade all tools<\/td>\n<\/tr>
uv tool uninstall ruff<\/code><\/td>\nUninstall ruff<\/code>\n<\/td>\n<\/tr>
\nuv tool install -e .<\/code>2<\/a><\/sup><\/td>\nInstall the current packageable project in editable mode<\/td>\n<\/tr><\/tbody><\/table>
Working with scripts 📜<\/a><\/h2>\n
<\/th>\n<\/th>\n<\/tr><\/thead>
uv init --script myscript.py<\/code><\/td>\nInitialise the script myscript.py<\/code>\n<\/td>\n<\/tr>
uv init --script myscript.py --python 3.X<\/code><\/td>\nInitialise the script myscript.py<\/code> and pin it to version 3.X<\/td>\n<\/tr>
uv add click --script myscript.py<\/code><\/td>\nAdd the dependency click<\/code> to the script<\/td>\n<\/tr>
uv remove click --script myscript.py<\/code><\/td>\nRemove the dependency click<\/code> from the script<\/td>\n<\/tr>
uv run myscript.py<\/code><\/td>\nRun the script myscript.py<\/code>\n<\/td>\n<\/tr>
uv run --python 3.X myscript.py<\/code><\/td>\nRun the script with the given Python version<\/td>\n<\/tr>
uv run --with click myscript.py<\/code><\/td>\nRun...<\/td><\/tr><\/tbody><\/table>","summary":"Cheatsheet with the most common and useful uv commands to manage projects and dependencies, publish projects, manage tools, and more.","date_modified":"2026-03-09T20:31:40+01:00","tags":["programming","python","uv"],"image":"\/user\/pages\/02.blog\/uv-cheatsheet\/thumbnail.webp"},{"title":"TIL #130 \u2013 Format Python code directly with uv","date_published":"2025-08-22T18:34:00+02:00","id":"https:\/\/mathspp.com\/blog\/til\/format-python-code-directly-with-uv","url":"https:\/\/mathspp.com\/blog\/til\/format-python-code-directly-with-uv","content_html":"
Today I learned you can format your Python code directly with uv.<\/p>\n\n
In uv version 0.8.13, released one or two days ago, uv added the command format<\/code> that allows you to format your Python code directly through the uv CLI.<\/p>\n
Update your uv<\/a><\/h2>\n
First and foremost, make sure you're rocking uv 0.8.13 or greater by running uv self update<\/code>.<\/p>\n
Format your code with uv<\/a><\/h2>\n
To format your code with uv you can simply run uv format<\/code>, which will use Ruff to format the code in your current directory:<\/p>\n
$ uv format<\/code><\/pre>\n
The idea is not to have uv replace Ruff; it's just so that you don't have to think about a separate tool if you don't want to.<\/p>\n
uv format<\/code> arguments<\/a><\/h2>\n
uv format<\/code> accepts the same arguments and options that ruff format<\/code> accepts, so you'll want to check the Ruff docs<\/a> to learn more.\nMy favourite option is --diff<\/code>, to take a look at the formatting diff without doing any formatting changes.<\/p>\n
As of now, the feature is marked as being experimental, which means it might change in the future!<\/p>","summary":"Today I learned you can format your Python code directly with uv.","date_modified":"2025-10-20T22:34:56+02:00","tags":["python","programming","productivity","uv"],"image":"\/user\/pages\/02.blog\/04.til\/130.format-python-code-directly-with-uv\/thumbnail.webp"},{"title":"Automatically pushing code changes during live coding with uv","date_published":"2025-05-14T10:25:00+02:00","id":"https:\/\/mathspp.com\/blog\/automatically-pushing-code-changes-during-live-coding-with-uv","url":"https:\/\/mathspp.com\/blog\/automatically-pushing-code-changes-during-live-coding-with-uv","content_html":"
This article shows the small script I use to automatically push code changes while live coding in talks or classes, improved with uv.<\/p>\n\n
One year ago I wrote a short TIL article where I showed how I automatically push code changes while I'm live-coding<\/a>.\nThe code I shared looked like this:<\/p>\n
from pathlib import Path\nfrom time import sleep\n\nfrom git import Repo\n\nrepo = Repo(Path(__file__).parent)\n\nwhile True:\n    repo.index.add(\"*\")\n    repo.index.commit(\"Auto sync commit\")\n    repo.remote().push()\n    sleep(60)<\/code><\/pre>\n
This code uses GitPython<\/code> to add all files in the folder that contains this script, adds a generic commit message, and pushes.\nThe script does this every minute, so when I'm teaching or doing any sort of live-coding, the repo I'm working off of gets updated every minute and participants can keep tabs on what I'm writing.<\/p>\n
Having used this for a while, there are two disadvantages to it:<\/p>\n
    \n
  1. I need to install GitPython<\/code> in a virtual environment in each repo I want to use this on; and<\/li>\n
  2. the script itself gets pushed to the repo, polluting it a bit.<\/li>\n<\/ol>\n
    (As I write this, I realised, I could fix 2. by adding the script to a file .gitignore<\/code>!)<\/p>\n
    To fix 1. and 2., and to improve my user experience a bit, I started using uv to inline the dependency on GitPython<\/code> and to turn it into a standalone executable<\/a>.<\/p>\n
    Assuming the script was called gitsync.py<\/code>, by doing uv add GitPython --script gitsync.py<\/code> and by adding the uv shebang<\/a>, the top of the script now looks like this:<\/p>\n
    #!\/usr\/bin\/env -S uv run\n\n# \/\/\/ script\n# requires-python = \">=3.13\"\n# dependencies = [\n#     \"gitpython\",\n# ]\n# \/\/\/<\/code><\/pre>\n
    I also tweaked the script structure a bit and now I use os.getcwd()<\/code> to figure out the current working directory when I run gitsync.py<\/code>:<\/p>\n
    #!\/usr\/bin\/env -S uv run\n\n# \/\/\/ script\n# requires-python = \">=3.13\"\n# dependencies = [\n#     \"gitpython\",\n# ]\n# \/\/\/\n\nimport os\nfrom time import sleep\n\nfrom git import Repo\n\ndef main() -> None:\n    repo_folder = os.getcwd()\n    print(f\"gitsync.py starting at {repo_folder}\")\n    repo = Repo(repo_folder)\n\n    while True:\n        repo.index.add(\"*\")\n        repo.index.commit(\"Auto sync commit\")\n        repo.remote().push()\n        sleep(60)\n\nif __name__ == \"__main__\":\n    main()<\/code><\/pre>\n
    This makes it so that I can put gitsync.py<\/code> in a directory that's in my PATH, and then use it from anywhere.\nNow, when I'm teaching, I just run gitsync.py &<\/code> and that starts syncing my code in the background.\nPretty cool!<\/p>","summary":"This article shows the small script I use to automatically push code changes while live coding in talks or classes, improved with uv.","date_modified":"2025-07-23T16:49:02+02:00","tags":["git","productivity","programming","python","uv"],"image":"\/user\/pages\/02.blog\/automatically-pushing-code-changes-during-live-coding-with-uv\/thumbnail.webp"},{"title":"TIL #122 \u2013 CLI tools with extra dependencies","date_published":"2025-05-04T09:34:00+02:00","id":"https:\/\/mathspp.com\/blog\/til\/cli-tools-with-extra-dependencies","url":"https:\/\/mathspp.com\/blog\/til\/cli-tools-with-extra-dependencies","content_html":"
    Today I learned you can use uv to install CLI tools with extra dependencies.<\/p>\n\n
    CLI tools with extra dependencies<\/a><\/h2>\n
    You can use uv<\/code> to install CLI tools in isolated virtual environments.\nE.g., uv tool install black<\/code> installs black<\/code> in an isolated venv.\nAfter installing, black<\/code> will be added to your path and you can use it directly.<\/p>\n
    When installing tools, you can use the option --with<\/code> to specify extra dependencies that will be available when you use the CLI tool you are installing.\nHere are two examples:<\/p>\n