[X-Guardian]

Description

pip install -r requirements.txt in the provider-add and provider-upgrade Python integration tests has been flaking with AssertionError: assert os.path.exists(pyc_path) from pip's wheel installer, mid-install of the JSII-generated cdktn / cdktn-provider-local wheels.
The assert fires in pip's .pyc byte-compilation step (cpython#86612 / bpo-42446) — pip expects a .pyc next to every .py, but compileall skips files under certain Python build configurations, leaving pip's assert with nothing to find.

Example failed job: https://github.com/open-constructs/cdk-terrain/actions/runs/26030565831/job/76518367284?pr=160

Fix

These tests only read/write requirements.txt to assert that cdktn provider add / cdktn provider upgrade edits it correctly — they never execute the installed packages. Passing --no-compile skips the bytecode step entirely and removes the failure mode without changing what's being tested.

Checklist

• I have updated the PR title to match CDKTN's style guide
• I have run the linter on my code locally
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if applicable
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works if applicable
• New and existing unit tests pass locally with my changes

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.