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

221 python uv #387

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

221 python uv #387

wants to merge 6 commits into from

Conversation

tommasodotNET
Copy link
Contributor

Closes #221

PR Checklist

  • Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
  • Based off latest main branch of toolkit
  • PR doesn't include merge commits (always rebase on top of our main, if needed)
  • New integration
    • Docs are written
    • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Contains NO breaking changes
  • Every new API (including internal ones) has full XML docs
  • Code follows all style conventions

@aaronpowell aaronpowell requested a review from Copilot January 15, 2025 00:43

Choose a reason for hiding this comment

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

Copilot reviewed 5 out of 11 changed files in this pull request and generated no comments.

Files not reviewed (6)
  • examples/python/uv-api/.gitignore: Language not supported
  • examples/python/uv-api/.python-version: Language not supported
  • src/CommunityToolkit.Aspire.Hosting.Python.Extensions/PublicAPI.Unshipped.txt: Language not supported
  • tests/CommunityToolkit.Aspire.Hosting.Python.Extensions.Tests/AppHostTests.cs: Evaluated as low risk
  • examples/python/CommunityToolkit.Aspire.Hosting.Python.Extensions.AppHost/Program.cs: Evaluated as low risk
  • src/CommunityToolkit.Aspire.Hosting.Python.Extensions/README.md: Evaluated as low risk
Copy link
Member

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

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

do we need to ensure that uv is installed as part of the CI job?

I think we might need to add it to the post-create.sh file for the devcontainer too.

Comment on lines +64 to +74
.WithArgs(context =>
{
// If the project is to be automatically instrumented, add the instrumentation executable arguments first.
if (!string.IsNullOrEmpty(instrumentationExecutable))
{
AddOpenTelemetryArguments(context);

// // Add the python executable as the next argument so we can run the project.
// context.Args.Add(pythonExecutable!);
}
});
Copy link
Member

Choose a reason for hiding this comment

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

may as well add this to the below if block and just have it resourceBuilder.WithArgs(AddOpenTelemetryArguments); since the if block is duplicated.

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.

Python uv and poetry modules
3 participants