Skip to content
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

Allow direct specification of Python requirements in .readthedocs.yaml #8956

Closed
mcarans opened this issue Feb 22, 2022 · 3 comments
Closed
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@mcarans
Copy link

mcarans commented Feb 22, 2022

Thanks for a useful project. Currently you can specify Python requirements in a file and put the path in .readthedocs.yaml. I want to suggest specifying requirements directly in .readthedocs.yaml to reduce the number of configuration files needed eg. something like

version: 2
mkdocs: {}  # tell readthedocs to use mkdocs
python:
  version: 3.7
  install:
  - dependencies: 
     - "pydoc-markdown"
     - "readthedocs-custom-steps==0.5.1"
@humitos
Copy link
Member

humitos commented Feb 22, 2022

Hi! Thanks for opening this issue. We already talked about this in #5572 (comment). That issue has a long discussion about an un-related thing but ends mentioning the support to install packages directly from the YAML.

@humitos humitos added Feature New feature Needed: design decision A core team decision is required labels Feb 22, 2022
@stsewd
Copy link
Member

stsewd commented Feb 22, 2022

Looks like a duplicated of #5572 then?

@mcarans
Copy link
Author

mcarans commented Feb 22, 2022

Closing, discussed in #5572

@mcarans mcarans closed this as completed Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants