Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[experimental] UV support for Python plugins #825

Draft
wants to merge 21 commits into
base: main
Choose a base branch
from
Draft

Conversation

lengau
Copy link
Contributor

@lengau lengau commented Aug 21, 2024

  • Have you signed the CLA?

@lengau lengau force-pushed the experimental/uv branch 2 times, most recently from 3138ed5 to 4e6a806 Compare August 21, 2024 21:45
self, *, properties: PluginProperties, part_info: infos.PartInfo
) -> None:
super().__init__(properties=properties, part_info=part_info)
use_uv_attr_name = f"{properties.plugin}_use_uv"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having a parameter like <plugin>-package-manager: uv (defaulting to pip) could allow us to use other package managers in the future (and avoid using a boolean property). There's also the option to have use-uv in build-attributes but that would not tie to Python-based plugins specifically.

def _get_find_python_interpreter_commands(self) -> list[str]:
"""Get the commands that find a staged Python interpreter.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could have these large helper scripts available as a separate utility to be invoked at build time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants