[x] Did you delete any extraneous prints/debugging code?
[ ] (If applicable) Did you add documentation for the feature?
[ ] (If applicable) Did you update the poetry.lock file if you updated the requirements in pyproject.toml?
[ ] (If applicable) Did you add a unit test demonstrating the PR?
[ ] (If applicable) Did you run this through the e2e integration tests?
[ ] (If applicable) Did you update the submodules in e2e/ if this feature depends on updated plugins?
Poetry 1.8 introduced a stricter virtualenv detection mechanism which doesn't recognize the RTD python virtualenv when running poetry install. To fix this, we manually specify the VIRTUAL_ENV when running poetry install in the RTD script. (see: https://github.com/readthedocs/readthedocs.org/pull/11152/)
harrisonliew
commented
6 months ago
Related PRs / Issues
Type of change:
Impact:
Contributor Checklist:
masteras the base branch?poetry.lockfile if you updated the requirements inpyproject.toml?e2e/if this feature depends on updated plugins?Poetry 1.8 introduced a stricter virtualenv detection mechanism which doesn't recognize the RTD python virtualenv when running
poetry install. To fix this, we manually specify theVIRTUAL_ENVwhen runningpoetry installin the RTD script. (see: https://github.com/readthedocs/readthedocs.org/pull/11152/)