[{'Text': '{"url":"https://dev.to/gautamvhavle/why-uv-refused-to-upgrade-my-package-and-why-it-was-actually-right-2ci4","title":"Why uv Refused to Upgrade My Package (And Why It Was Actually Right) - DEV Community","description":"# Removed the legacy-locked package numba # ← goodbye old friend, you&#x27;re holding us back # Or alternatively, waited for numba&#x27;s numpy 2.0 compatible release # and pinned to that specific version · numpy&gt;=2.0,&lt;3.0 pandas&gt;=2.2,&lt;3.0 scipy&gt;=1.13,&lt;2.0 scikit-learn&gt;=1.5,&lt;2.0 matplotlib&gt;=3.8,&lt;4.0 · With a logically consistent dependency graph, I ran: ... No force flags. No hacks. No deleting lockfiles. No stackoverflow copypasta. It. Just. Worked. ✨ ... When uv says &quot;no,&quot; it&#x27;s because you&#x27;re asking for the impossible.","extra_snippets":["I thought uv was being annoying. Turns out, it saved me from breaking my entire project. Here\'s the... Tagged with uv, python, dependencyinversion, programming.","# Removed the legacy-locked package numba # ← goodbye old friend, you\'re holding us back # Or alternatively, waited for numba\'s numpy 2.0 compatible release # and pinned to that specific version · numpy>=2.0,<3.0 pandas>=2.2,<3.0 scipy>=1.13,<2.0 scikit-learn>=1.5,<2.0 matplotlib>=3.8,<4.0 · With a logically consistent dependency graph, I ran: ... No force flags. No hacks. No deleting lockfiles. No stackoverflow copypasta. It. Just. Worked. ✨ ... When uv says \\"no,\\" it\'s because you\'re asking for the impossible.","uv isn\'t being stubborn. It\'s being honest. Your dependency graph is a specification of reality, and if that specification is contradictory, no tool can make it work — they can only pretend to.","What started as a \\"quick 5-minute fix\\" turned into a deep dive into how uv (the blazingly fast Python package manager) actually thinks. And honestly?"]}{"url":"https://github.com/astral-sh/uv/issues/6781","title":"Add the option to `uv add` to pin to latest version of package · Issue #6781 · astral-sh/uv","description":"Current behaviour <strong>When you run uv add without specifying a version constraint, it defaults to &gt;= latest version</strong>. I think this is a good default. uv init --app --python 3.12.5 uv add black cat pyproject.toml # [project] # name = &quot;example-...","extra_snippets":["Current behaviour When you run uv add without specifying a version constraint, it defaults to >= latest version. I think this is a good default. uv init --app --python 3.12.5 uv add black cat pyproject.toml # [project] # name = \\"example-...","The only downside to the above, is that it requires me to know the latest version of black. This is easy to find, searching on PyPI. But, I find this is a common enough task I do that I would like a shorthand to install the latest version, but also pin to that specific version.","uv add black --pin-to-latest cat pyproject.toml # [project] # name = \\"example-2\\" # version = \\"0.1.0\\" # description = \\"Add your description here\\" # readme = \\"README.md\\" # requires-python = \\">=3.12.4\\" # dependencies = [ # \\"black==24.8.0\\", # ]","uv init --app --python 3.12.5 uv add black cat pyproject.toml # [project] # name = \\"example-2\\" # version = \\"0.1.0\\" # description = \\"Add your description here\\" # readme = \\"README.md\\" # requires-python = \\">=3.12.4\\" # dependencies = [ # \\"black>=24.8.0\\", # ]"]}{"url":"https://github.com/astral-sh/uv/issues/17113","title":"`uv add -U package` claims unsatisfiable with pinned dependency and constraints-dependencies configured · Issue #17113 · astral-sh/uv","description":"It also defines package constraints in the constraints-dependencies, also a pinned version. Specifically - starting with a working project with both dependencies and constraints-dependencies configured with zapp==3.20.2, change the constraints-dependencies to be zapp==3.21.0 · My assumption is I could run uv add -U zipp and the dependency value and lock file would both get updated to the new constraint version - but I get this instead: root@3c0e7cfdf989:/workspaces/neptune-bulk# uv add -U zipp × No solution found when resolving dependencies: ╰─▶ Because your project depends on zipp==3.20.2 and zipp==3.21.0, we can conclude that your project&#x27;s requirements are unsatisfiable.","extra_snippets":["uv add -U package claims unsatisfiable with pinned dependency and constraints-dependencies configured#17113 ... This might be user error or a doc improvement, not a code bug. Our pyproject.toml specifies pinned dependency versions (so package==x.y.z not ranges).","It also defines package constraints in the constraints-dependencies, also a pinned version. Specifically - starting with a working project with both dependencies and constraints-dependencies configured with zapp==3.20.2, change the constraints-dependencies to be zapp==3.21.0 · My assumption is I could run uv add -U zipp and the dependency value and lock file would both get updated to the new constraint version - but I get this instead: root@3c0e7cfdf989:/workspaces/neptune-bulk# uv add -U zipp × No solution found when resolving dependencies: ╰─▶ Because your project depends on zipp==3.20.2 and zipp==3.21.0, we can conclude that your project\'s requirements are unsatisfiable.","Am I running the wrong command to trigger the package and pyproject.toml upgrade, or is there a technical issue here? Changing the pinned project dependencies to be ranges did allow syncing to happen, but still doesn\'t update the target version"]}{"url":"https://github.com/astral-sh/uv/issues/13551","title":"uv doesnt update the package version when installed with uv pip install · Issue #13551 · astral-sh/uv","description":"Summary When I run uv add package-name, it installs an older version of the package unless I manually specify the version with uv pip install package-name==x.x.x. Why is that? After updating the pa...","extra_snippets":["Summary When I run uv add package-name, it installs an older version of the package unless I manually specify the version with uv pip install package-name==x.x.x. Why is that? After updating the package version, how do I update the lock ...","After updating the package version, how do I update the lock file? Shouldn’t it update automatically? Running uv lock doesn’t seem to do anything, and uv sync reverts the package back to the old version listed in uv.lock."]}{"url":"https://medium.com/@yanxingyang/how-to-updating-project-dependencies-with-uv-c9247040be27","title":"How to Updating Project Dependencies with uv ? | by Yanxing Yang | Medium","description":"The key difference here is that package versions are specified as ranges (e.g., httpx&gt;=0.27.0, fastapi&gt;=0.114.2). <strong>This happens when you initially install a package with uv add httpx</strong>—if the latest version at the time is 0.27.0, pyproject.toml ...","extra_snippets":["Want to keep your Python dependencies up-to-date effortlessly?","The key difference here is that package versions are specified as ranges (e.g., httpx>=0.27.0, fastapi>=0.114.2). This happens when you initially install a package with uv add httpx—if the latest version at the time is 0.27.0, pyproject.toml records httpx>=0.27.0 to allow future upgrades. If you instead use uv add httpx==0.27.0, the version is pinned, making upgrades harder.","The uv.lock file records the exact versions of the packages in the current environment. Think of pyproject.toml as defining version ranges, while uv.lock specifies the concrete versions.","uv sync --upgrade-package httpx Resolved 18 packages in 204ms Prepared 1 package in 20ms Uninstalled 1 package in 18ms Installed 1 package in 34ms - httpx==0.27.0 + httpx==0.28.1 · The output shows that httpx was upgraded from 0.27.0 to 0.28.1. Similarly, if another package (e.g., requests) has updates (e.g., 2.32.3), you can upgrade it with: ... Here, httpx is pinned to 0.27.0."]}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/13551","data":{"forum_name":"github.com","num_answers":1,"title":"uv doesnt update the package version when installed with uv pip install","top_comment":"Summary When I run uv add package-name, it installs an older version of the package unless I manually specify the version with uv pip install package-name==x.x.x. Why is that? After updating the pa..."}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/6747","data":{"forum_name":"github.com","num_answers":5,"title":"List specifier used to install a tool","top_comment":"Currently (uv v0.3.5) if a constraint is used with uv tool install the version/restriction is pinned and subsequent uv tool upgrade commands might not update to a newer release. E.g. `uv tool insta..."}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/13785","data":{"forum_name":"github.com","num_answers":6,"title":"`uv sync` updates `uv` itself away from the pinned version","top_comment":"Summary In my pyproject.toml I have: [tool.uv] required-version = \\"==0.7.8\\" When I run astral-sh/setup-uv@v6 in a Github workflow it correctly installs the right version: Found required-v..."}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/6794","data":{"forum_name":"github.com","num_answers":77,"title":"Upgrade dependencies in `pyproject.toml` (`uv upgrade`)","top_comment":"why? when i want to update all the dependencies in a project, it can be tedious to manually search for and update each and every dependency. additionally, for application projects (not libraries), i like to be able to squizz the pyproject file for an easy overview of which dependencies are ..."}}{"mutated_by_goggles":false,"url":"https://www.reddit.com/r/learnpython/comments/1rcphaf/uv_tool_install_git_ignores_the_pinned_python/","data":{"forum_name":"r/learnpython","num_answers":3,"score":"0","title":"uv tool install git+ ignores the pinned python version","question":"<p>\\n      Hi,\\n    </p><p>\\n      My project contains .python-version file with 3.13. When I build and install the project via\\n    </p><p>\\n      uv build\\n    </p><p>\\n      uv tool install dist/...whl\\n    </p><p>\\n      the app runs on 3.13.\\n    </p><p>\\n      When I test it on another box like\\n    </p><p>\\n      uv tool install git+<a rpl class=\\"relative pointer-events-auto a cursor-pointer\\n  \\n  \\n  \\n  \\n  underline\\n  \\" href=\\"https://github.com/me/myproject\\" rel=\\"noopener nofollow ugc\\" target=\\"_blank\\">https://github.com/me/myproject</a>\\n    </p><p>\\n      the installed app runs on the current system version (3.14). Is there a way to make uv respect the .python-version on github?\\n    </p>","top_comment":"From uv documentation https://docs.astral.sh/uv/concepts/tools/#python-versions Each tool environment is linked to a specific Python version. This uses the same Python version discovery logic as other virtual environments created by uv, but will ignore non-global Python version requests like .python-version files and the requires-python value from a pyproject.toml. The --python option can be used to request a specific version. See the Python version documentation for more details."}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/18178","data":{"forum_name":"github.com","num_answers":5,"title":"uv lock --upgrade-package does not upgrade without specifying version","top_comment":"Summary Based on the docs \\"To upgrade a single package to the latest version\\" we use --upgrade-package https://docs.astral.sh/uv/concepts/projects/sync/#upgrading-locked-package-versions ..."}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/6692","data":{"forum_name":"github.com","num_answers":12,"title":"What is the intended workflow for updating dependencies with uv?","top_comment":"Hi, I am looking into uv for several days now and try to determine whether my team should switch from poetry to uv. One thing that seems completely absent in the documentation is a way to update de..."}}{"mutated_by_goggles":false,"url":"https://stackoverflow.com/questions/79475051/whats-the-difference-between-uv-lock-upgrade-and-uv-sync","data":{"forum_name":"stackoverflow.com"}}{"mutated_by_goggles":false,"url":"https://github.com/astral-sh/uv/issues/5797","data":{"forum_name":"github.com","num_answers":6,"title":"`uvx` doesn\'t upgrade when existing tool is installed","top_comment":"This is a confusing workflow: ❯ uv tool install ruff==0.0.60 Resolved 1 package in 5ms Installed 1 package in 3ms + ruff==0.0.60 Installed 1 executable: ruff ❯ uvx ruff --version ruff 0.0.60 ❯ uvx ..."}}{"mutated_by_goggles":false,"url":"https://www.reddit.com/r/Python/comments/1pqyzse/uv_update_recommendations/","data":{"forum_name":"r/Python","num_answers":34,"score":"39","title":"uv update recommendations","question":"<p>\\n      After adopting astral&#39;s uv last August, I did my first check for updates and found <a rpl class=\\"relative pointer-events-auto a cursor-pointer\\n  \\n  \\n  \\n  \\n  underline\\n  \\" href=\\"https://github.com/astral-sh/uv/releases\\" rel=\\"noopener nofollow ugc\\" target=\\"_blank\\">astral releases</a> -- pretty much non-stop.\\n    </p><p>\\n      What are other folks&#39; experiences with updates? Is updating to the latest and greatest a good strategy, or is letting others &quot;jump in the water&quot; first prudent?\\n    </p>","top_comment":"I always use the latest version, rarely had issues with it. (Note: I work on uv)"}}{"mutated_by_goggles":false,"url":"https://stackoverflow.com/questions/79581046/lock-specific-dependency-versions-with-uvx-uv-tool-run","data":{"forum_name":"stackoverflow.com"}}{"mutated_by_goggles":false,"url":"https://www.reddit.com/r/learnpython/comments/1jbo88t/uv_for_python_project_and_version_management/","data":{"forum_name":"r/learnpython","num_answers":6,"score":"7","title":"UV for Python Project and Version Management","question":"<p>\\n      Getting started with the <a rpl class=\\"relative pointer-events-auto a cursor-pointer\\n  \\n  \\n  \\n  \\n  underline\\n  \\" href=\\"https://docs.astral.sh/uv/\\" rel=\\"noopener nofollow ugc\\" target=\\"_blank\\">UV Astral</a> for python development.\\n    </p><p>\\n      Just noted, uv works with a few important files in the project root, but their exact purpose and roles are not clear to me\\n    </p><ul>\\n        <li>\\n      <p>\\n      <code>pyproject.toml</code>\\n    </p>\\n    </li><li>\\n      <p>\\n      <code>.python-version</code>\\n    </p>\\n    </li><li>\\n      <p>\\n      <code>uv.lock</code>\\n    </p>\\n    </li>\\n      </ul><p>\\n      Most notably, the concrete questions are\\n    </p><ul>\\n        <li>\\n      <p>\\n      Where does <code>uv</code>get the exact python version? Is it <code>pyproject.toml</code> or <code>.python-version</code>? If they give different or contradictory requirement, which one takes priority, and why the need to mention the python version twice?\\n    </p>\\n    </li><li>\\n      <p>\\n      What about the <code>uv.lock</code>? If the <code>pyproject.toml</code>file has the precise python version and those of the libraries installed (example below), is that a <em>complete</em> specification of the environment?\\n    </p>\\n    </li>\\n      </ul><pre>\\n[project]\\nname = &quot;uv-trial&quot;\\nversion = &quot;0.1.0&quot;\\ndescription = &quot;Add your description here&quot;\\nreadme = &quot;README.md&quot;\\nrequires-python = &quot;==3.12.8&quot;\\ndependencies = [&quot;tensorflow==2.18.0&quot;]</pre><ul>\\n        <li>\\n      <p>\\n      Should the <code>uv.lock</code>be committed to Git or is it a volatile artefact, that is meant for <code>uv</code>&#39;s internal use? If it has a lot of detail that are irrelevant to the application developer, is it necessary to track via Git?\\n    </p>\\n    </li>\\n      </ul>","top_comment":"pyproject.toml is a config file used for package builders https://packaging.python.org/en/latest/guides/writing-pyproject-toml/ uv.lock is your exact enviroment config https://docs.astral.sh/uv/guides/projects/#python-version and yes, based on their documents (link above again) This file should be checked into version control, allowing for consistent and reproducible installations across machines. edit: changed system to environment"}}{"mutated_by_goggles":false,"url":"https://www.reddit.com/r/Python/comments/1gqh4te/uv_after_050_might_be_worth_replacing/","data":{"forum_name":"r/Python","num_answers":127,"score":"400","title":"uv after 0.5.0 - might be worth replacing Poetry/pyenv/pipx","question":"<p>\\n      uv is rapidly maturing as an open-source tool for Python project management, reaching a full-featured capabilities with recent versions 0.4.27 and 0.5.0, making it a strong alternative to Poetry, pyenv, and pipx. However, concerns exist over its long-term stability and licensing, given Astral&#39;s venture funding position.\\n    </p><p>\\n      <a rpl class=\\"relative pointer-events-auto a cursor-pointer\\n  \\n  \\n  \\n  \\n  underline\\n  \\" href=\\"https://open.substack.com/pub/martynassubonis/p/python-project-management-primer-a55\\" rel=\\"noopener nofollow ugc\\" target=\\"_blank\\">https://open.substack.com/pub/martynassubonis/p/python-project-management-primer-a55</a>\\n    </p>","top_comment":"Nice article. Thanks. I wasn\'t aware poetry\'s lead author had moved on from it. He had made so much noise on reddit when he marketed poetry. It was quite relentless at the time. Goes to show you should never attach yourself too much to any of these tools. They come and go."}}'}]