Context
In microsoft/typespec#11522 — Migrate Python checks to CI Gate, Python checks are being migrated from Azure DevOps pipelines to GitHub Actions. During review, a reviewer asked whether obsolete files should be deleted. The author confirmed that unnecessary scripts in http-client-python could be removed, but deferred the cleanup to a separate PR to keep the migration focused.
Follow-up for typespec-azure
Review the corresponding Azure Python emitter CI setup in packages/typespec-python and its related pipeline configuration for the same cleanup opportunity.
- Identify legacy CI scripts and pipeline files made obsolete by the CI Gate migration.
- Confirm they are not used by active CI workflows, release automation, or local development before removing them.
- Remove obsolete files and update any affected script references or documentation.
- Preserve scripts still required by Azure-specific workflows.
Acceptance criteria
Unused legacy Python CI scripts and configuration are removed, no dangling references remain, and the supported Python CI and local development workflows continue to work.
The linked discussion specifically concerns upstream packages/http-client-python; this issue tracks the applicable Azure-side follow-up rather than assuming identical files are obsolete here. Further CI performance optimizations mentioned in the upstream PR are outside this cleanup's scope.
Context
In microsoft/typespec#11522 — Migrate Python checks to CI Gate, Python checks are being migrated from Azure DevOps pipelines to GitHub Actions. During review, a reviewer asked whether obsolete files should be deleted. The author confirmed that unnecessary scripts in
http-client-pythoncould be removed, but deferred the cleanup to a separate PR to keep the migration focused.Follow-up for typespec-azure
Review the corresponding Azure Python emitter CI setup in
packages/typespec-pythonand its related pipeline configuration for the same cleanup opportunity.Acceptance criteria
Unused legacy Python CI scripts and configuration are removed, no dangling references remain, and the supported Python CI and local development workflows continue to work.
The linked discussion specifically concerns upstream
packages/http-client-python; this issue tracks the applicable Azure-side follow-up rather than assuming identical files are obsolete here. Further CI performance optimizations mentioned in the upstream PR are outside this cleanup's scope.