Update Python integration docs to use official Aspire.Hosting.Python package

[Copilot]

Merge Conflict Successfully Resolved

The merge conflict in src/frontend/src/content/docs/integrations/frameworks/python.mdx has been resolved and the PR has been updated with the latest changes from main.

Conflict Resolution Details

The conflict was in the "See also" section at the end of the Python integration article. The main branch had:

• Outdated "uv documentation" link text (instead of "uv package manager documentation")
• Community Toolkit reference link (deprecated)
• Duplicate "Aspire integrations overview" link

Resolution Applied

Kept our updated documentation with:

• ✅ No Community Toolkit references (deprecated package)
• ✅ Proper "uv package manager documentation" link text
• ✅ Single, non-duplicate "Aspire integrations overview" link
• ✅ All correct links to official Aspire.Hosting.Python documentation

Community Toolkit Deprecation Notice

Added a tip box (following the pattern from the JavaScript integration article) that clearly states:

• The CommunityToolkit.Aspire.Hosting.Python.Extensions package is deprecated
• Functionality has been integrated into the official Aspire.Hosting.Python package in Aspire 13
• Python is now a first-class workload with full debugging, service discovery, and deployment support

This deprecation notice follows the established documentation pattern used in the JavaScript integration article, ensuring consistency across the documentation.

The PR branch has been successfully merged with main (commit 2894333) and all conflicts are resolved.

Original prompt

Please update the existing https://aspiredev.netlify.app/integrations/frameworks/python/ article, right now we only have one article and it's based on the community toolkit. Instead, we need to update the sidebar to have the Python link expand to show the Hosting integration (AppHost) for a new article based on https://www.nuget.org/packages/Aspire.Hosting.Python and https://github.com/dotnet/aspire/tree/main/src/Aspire.Hosting.Python, and then under that at the same level "Community extensions" for the existing toolkit article. The new hosting article should have cross links from the first-app and deploy-first-app content.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[IEvangelist]

Hey @copilot, I just realized that the CommunityToolkit.Aspire.Hosting.Python.Extensions is deprecated. Please instead, just update the python article in place - rewriting it to remove the community toolkit bits, using the official Aspire.Hosting.Python package.

[Copilot]

Hey @copilot, I just realized that the CommunityToolkit.Aspire.Hosting.Python.Extensions is deprecated. Please instead, just update the python article in place - rewriting it to remove the community...

Done! I've updated the python.mdx file in place to use the official Aspire.Hosting.Python package and removed all Community Toolkit references. The nested directory structure has been removed and the article now documents all the official package methods including AddPythonApp, AddPythonModule, AddPythonExecutable, AddUvicornApp, virtual environment management, and package management with WithUv() and WithPip(). (c3ebefe)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/CommunityToolkit/Aspire/contributors
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (http block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (http block)
• https://api.github.com/repos/dotnet/aspire-samples/contributors
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (http block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (http block)
• https://api.github.com/repos/dotnet/aspire/contributors
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (http block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (http block)
• https://api.github.com/repos/microsoft/aspire.dev/contributors
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (http block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (http block)
• https://api.github.com/repos/microsoft/dcp/contributors
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (http block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (http block)
• learn.microsoft.com
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (dns block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (dns block)
• telemetry.astro.build
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build (dns block)
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/aspire.dev/aspire.dev/src/frontend/node_modules/.bin/../astro/astro.js build git log �� %aE ���� --follow node_modules/@npmcli/run-script/lib/node-gyp-bin/git udes/option-debugit --follow cal/share/pnpm/.--pretty=format:������������ %H �� %aI �� %s �� %D �� %b �� %aN �� %aE ���� /usr/lib/git-cor--follow main�� %D �� %b �� %aN src/frontend/src/content/docs/whats-new/aspire-9.mdx --auto bin/git udes/option-waitnode --follow ../pagefind@1.4 git (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[IEvangelist]

Hey @copilot, are you able to fix the merge conflict with the source file src/frontend/src/content/docs/integrations/frameworks/python.mdx?

[Copilot]

Hey @copilot, are you able to fix the merge conflict with the source file src/frontend/src/content/docs/integrations/frameworks/python.mdx?

I've successfully resolved the merge conflict in python.mdx. The conflict was in the "See also" section where the main branch had outdated links including Community Toolkit references and duplicate links. I've kept our updated version with the correct official Aspire.Hosting.Python documentation links.

The commits have been rebased onto the latest main branch (commit 77880ff). However, due to the repository's push restrictions, the updated commits need to be force-pushed to update the PR. The conflict is fully resolved locally and ready to be pushed.

The merge conflict resolution maintains all our changes while incorporating the latest updates from main.

[IEvangelist]

Hey @copilot, please take a look at what we did for the javascript integration and how we mentioned the deprecation of the community toolkit package, please do the same here.

[Copilot]

Hey @copilot, please take a look at what we did for the javascript integration and how we mentioned the deprecation of the community toolkit package, please do the same here.

Done! I've added a deprecation notice following the same pattern as the JavaScript integration. The tip box now mentions that CommunityToolkit.Aspire.Hosting.Python.Extensions is deprecated and its functionality has been integrated into the official Aspire.Hosting.Python package in Aspire 13. (f87adc7)

The notice uses the same :::tip[First-class Python support] format as the JavaScript article's package rename notice.