-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Unable to build docs with poetry #6151
Comments
Hi @OK-UNDP! Can you link your project URL and build URL that it's failing? We do install the packages with There were some ideas to support poetry and pipfile (#3181) but considering the amount of work, we are not ready for it. |
@OK-UNDP please check #4912 (comment) |
Hi @humitos, the latest build URL is this one. I also fixed the RTD project URL in the original post above. Pip 19.2.3 docs mention regarding PEP-517 that:
My [build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api" However, when I do Hi @stsewd, you would have to spell it out for me. I have wiped the environment multiple times but it didn't help. |
@OK-UNDP can you try updating/recreating the poetry.lock file? This repo works on rtd, and the lock file looks kind of different https://github.com/zalando-incubator/transformer/blob/master/poetry.lock (I'm not familiar with poetry) |
@stsewd, I figured it out. Here is the issue, which is not related to RTD it seems (would be glad for suggestions where I should file it ( Issue SummaryThe initial issues was that Further troubleshooting identified that when So, this is not the RTD's issue, but some intricacy of How to re-create the issue
How to resolve the issue
|
@OK-UNDP wow, thanks for so descriptive solution :) I think you should check if the |
Details
Expected Result
I have the V2 .readthedocs.yaml in a feature branch of my project that defines:
Since I use
poetry
and extras defined in pyproject.toml, I would expect RTD to install[docs]
extras and build to succeed.Actual Result
Instead, builds for the feature branch version fail due to unavailable dependencies. Package install step shows this:
Perhaps I am doing something wrong, so I would be grateful if somebody could point me to the right direction.
The text was updated successfully, but these errors were encountered: