-
Notifications
You must be signed in to change notification settings - Fork 48
Description
Feature idea
As a user, I want to automatically use the newest version of uv.
Additional context
The uv UrlUpdater needs to be implemented.
The Python UrlUpdater needs to be adjusted as follows, since downloads are no longer handled via urls:
The Python version url folders no longer need to contain actual urls (download is happening through uv)The version folders still need some type of url-file for version auto-completion and version validation (this file can be empty but must be namedurls)- uv supports every python version starting from version
3.8.2,so folders for earlier versions should be removed
Related/Dependent issues
Update:
The existing urls for Python may not be very important but devonfw-ide is still in use and also uses these files.
With devonfw-ide it is possible to install Python this way (with some flaws).
We should not break legacy compatibility for no reason.
For auto-completion we need the version folders in the ide-urls git. And for every tool where we have them they are filled with urls files and according checksums as well as status.json. I do not see why we should violate this pattern for Python.
If we want to improve the PythonUrlUpdater, we should try to make the URLs point to portable downloads instead of global installers but this is not required currently and should be done in a different story if we do it at all.
uv supports every python version starting from version
3.8.2, so folders for earlier versions should be removed
We could also find other ways so IDEasy could say that the according version is not supported without deleting the old versions...
Given the current context, there's no need to adjust the PythonUrlUpdater. The constraint preventing IDEasy from using Python versions below 3.8.2 has already been addressed in #1442.
Therefore, this issue is solely focused on implementing a new UvUrlUpdater for the project.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status