Skip to content

Add guide for requirements from #3636 #4212

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

Merged
merged 3 commits into from
Jun 15, 2018
Merged

Conversation

agjohnson
Copy link
Contributor

The original PR got confused about files changes. I cherry picked these from the
history. Hopefully this is most of the changes

Closes #3636

The original PR got confused about files changes. I cherry picked these from the
history. Hopefully this is most of the changes

Closes #3636
@agjohnson agjohnson requested a review from a team June 8, 2018 21:20
@agjohnson
Copy link
Contributor Author

I think we've discussed most of the content changes at this point. I guess we're mostly concerned with if these files look the same as the original. A quick glance looks like things are okay though.

- Documenting multiple packages
- setup.py not in root directory

See :ref:`faq_document_package_not_at_root`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use the autosectionlabel feature here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not too concerned with the content, I'm not that author here

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with Santos here so we have most of our docs using the same pattern. The ref would look like:

:ref:`faq:Can I document a python package that is not at the root of my repository?`

Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good.

I just made some comments to be considered but I don't want to block on them.


Using the YAML configuration file
---------------------------------
The recommended approach for specifying a pip requirements file is to use a readthedocs.yml file.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd use `readthedocs.yml` here (quotes for code)



.. _`pip user guide`: : https://pip.pypa.io/en/stable/user_guide/#requirements-files
.. _`conda and environment.yml`: : https://conda.io/docs/user-guide/tasks/manage-environments.html
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these : duplicated here?

- Documenting multiple packages
- setup.py not in root directory

See :ref:`faq_document_package_not_at_root`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with Santos here so we have most of our docs using the same pattern. The ref would look like:

:ref:`faq:Can I document a python package that is not at the root of my repository?`

Additional Uses
~~~~~~~~~~~~~~~
- Documenting multiple packages
- setup.py not in root directory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand this section. I think it would be better if an introduction paragraph is added instead of just a two item list with a link.

.. code-block:: yaml

conda:
file: environment.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some weird spaces here: probably tabs mixed with spaces.

@ericholscher
Copy link
Member

Cleaned this up and should be merge ready.

@ericholscher ericholscher merged commit bd9cd6a into master Jun 15, 2018
@stsewd stsewd deleted the agj/requirements-docs-fixup branch August 15, 2018 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants