Quick guide
Can macCurrent update Python packages on a Mac?
macCurrent checks and updates eligible Python packages in supported environments on macOS 15 or later. Open Packages > Python, review the Python version and environment path, then choose Update or Update Selected. Supported routes include ordinary virtual environments, uv tools, pipx, Conda, Poetry, Pipenv and uv projects. Each route has its own requirements; a newer published version does not always qualify for installation.
How to update Python packages with macCurrent
- Run Scan, then open Packages > Python. Select the installed package copy you want to update.
- Review Python Environment for its Python version, environment path and owning manager. The same package in two environments is two installations.
- For an ordinary environment, confirm that its packages come from public PyPI. Review any project, dependency-group or optional-feature choices when prompted.
- Choose Update or Update Selected for eligible updates. Download Only can save a checked update for Install Downloaded later. Keep the environment idle during installation.
- Review the installed result. If an operation needs recovery, read the package details before using Restore Environment.
Use case: update a CLI installed with pipx
You use a Python command-line application in a pipx-managed environment and want to review its update alongside your other developer tools.
- Find the package in Packages > Python and confirm its pipx environment and interpreter.
- Review the eligible update and manager-specific requirements.
- Keep the environment idle and start the update after compatibility checks and the rehearsal pass.
The supported pipx route accounts for the tool’s main package, injected packages and installation records. macCurrent checks the result in that environment.
Private package sources and unsupported manager settings can prevent an update. Updating the tool does not change Python in unrelated environments.
Use case: bring a uv project environment up to its existing lock
Your team has already committed a newer dependency version in uv.lock, but your supported local project environment still contains the older installed version.
- Select the package in its project environment and review the project association.
- Confirm the workspace, dependency groups and optional features used by that environment.
- Install an eligible update that is already selected by the existing project and lock file.
macCurrent follows the existing lock selection and preserves project and source files. It checks and rehearses the environment change before installation.
If the newest published release is not in the lock file, use the project’s manager to revise dependency choices first. macCurrent does not generate a new lock file to force that release into the project.
Which Python environments can update?
| Environment | How macCurrent handles it |
|---|---|
| Ordinary virtual environments | Requires public PyPI confirmation and a supported existing Python installation; checks the complete environment before changes. |
| uv tools and pipx | Uses a supported manager-specific route that accounts for tool records and injected packages. |
| Conda environments | Uses supported Conda package and channel records rather than treating the environment as an ordinary pip installation. |
| Poetry and Pipenv projects | Follows the existing lock file and preserves project and source files. |
| uv projects and workspaces | Follows the existing uv.lock and confirmed workspace, dependency groups and optional features. |
Project and native-manager routes require CPython 3.11 or later within their supported profiles. Discovery can include installations that cannot be updated. Private package sources, arbitrary build hooks and native local extension builds are outside the supported update routes.
Why a newer PyPI version may not install
A package can need a different Python version, conflict with another installed requirement, or fall outside a project’s lock file. macCurrent checks compatibility across the environment and rehearses the update in a private copy before installation. A failed or incomplete check stops the update.
For Poetry, Pipenv and uv projects, macCurrent does not create a new lock file to make a newer package fit. Update the project’s dependency choices through its manager first. The uv locking and syncing guide explains how a lock file selects package versions.
Qualified pure-Python uv_build workspace projects can rebuild when the existing project and lock already select a newer version. Rebuilding the same version or compiling native local extensions is outside this route.
Recovery and Python runtime updates
Restore Environment replaces the entire environment with its saved copy. It does not overwrite project or source files. If ownership or project files have changed, macCurrent retains the recovery copy and explains why it cannot proceed. Scheduled automatic Python installation is disabled.
Updating a package does not upgrade Python itself. macCurrent supplies its package-management tools, so you do not need to install uv or open a terminal for supported package updates. A working supported Python installation must already exist. See how Python runtime updates work.
If you manage an environment yourself, the Python Packaging User Guide explains pip and virtual environments. Confirm the interpreter and environment before changing packages.
Frequently asked questions
Can macCurrent update Python packages on a Mac?
Yes. macCurrent checks and updates eligible Python packages in supported environments. Open Packages > Python, verify the Python version and environment path, and use Update or Update Selected. Compatibility, package sources and the owning manager determine whether installation is available.
Does macCurrent support pipx, uv and Conda?
Supported routes include uv tools, pipx, Conda and ordinary virtual environments. Poetry, Pipenv and uv project environments follow their existing lock files. Discovery does not guarantee installation support; each route must pass its own checks.
Will macCurrent rewrite my Python project lock file?
No. Supported Poetry, Pipenv and uv project updates follow the existing lock file and preserve project and source files. Use the project manager to change dependency choices or generate a new lock file.
Do I need to install uv to use macCurrent?
No. macCurrent supplies its package-management tools for supported Python package updates. Each environment still needs a working supported Python installation.
Can Python packages update automatically on a schedule?
Scheduled automatic Python installation is disabled. Review the package, environment and compatibility result before starting an eligible update.
Does Restore Environment restore just one package?
No. Restore Environment replaces the entire environment with its saved copy. Project and source files are not overwritten, and recovery can be blocked if ownership or project files have changed.