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

Add first class support for running python apps with specified modules #6244

Open
davidfowl opened this issue Oct 11, 2024 · 1 comment
Open
Labels
area-integrations Issues pertaining to Aspire Integrations packages python
Milestone

Comments

@davidfowl
Copy link
Member

There's no first-class overload or different method to support running python apps where a module is the entrypoint and figuring out how to invoke the overloads that are there such that a module is used as the entrypoint is confusing due to the parameter counts and names. When combined with the previous point, this is what is required to run a Python app using a module as the entrypoint:

// You need to pass "-m" as the value for the 'scriptPath' parameter:
builder.AddPythonApp("python-app-module", "../PythonApp", scriptPath: "-m", ["module-name", "moduleArg1"]);
@davidfowl davidfowl added area-integrations Issues pertaining to Aspire Integrations packages enhancement python labels Oct 11, 2024
@davidfowl davidfowl added this to the 9.0 milestone Oct 11, 2024
@joperezr joperezr modified the milestones: 9.0, Backlog Oct 14, 2024
@robotdad
Copy link

We have someone looking to run one of our Python services using Aspire and this is the current blocker. They are going to investigate if they can create an extension to support uv integration which would also resolve it as that is our primary path right now outside of Aspire.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-integrations Issues pertaining to Aspire Integrations packages python
Projects
None yet
Development

No branches or pull requests

3 participants