-
Notifications
You must be signed in to change notification settings - Fork 9
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
Collect common links under custom file #82
Conversation
f642329
to
58e7b72
Compare
doc/source/links.rst
Outdated
.. _PyAEDT: https://github.com/pyansys/pyaedt | ||
.. _PyMAPDL: https://github.com/pyansys/pymapdl | ||
.. _PyAnsys: https://docs.pyansys.com/ | ||
.. _PyAnsys PyPI: https://pkgs.dev.azure.com/pyansys/_packaging/pyansys/pypi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link does no longer work.
8f9bab5
to
a6b67c5
Compare
Co-authored-by: Maxime Rey <[email protected]>
4cc82cb
to
fdefe74
Compare
cd1fa2b
to
d99348e
Compare
The error in the PDF building process is caused by this PR, as the nightly build ran without problems. Reading the logs locally to identify the problem... |
This is likely to be introduced by some "infinite-loop" when solving links. This works fine in the HTML builder but not sure if will do so for the PDF. |
This guide might be an alternate approach to this: https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html#setup-external-links |
placing them into the ``vars`` list, all while following the Style | ||
Guide for Python Code, defined in `PEP 8`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
placing them into the ``vars`` list, all while following the Style | |
Guide for Python Code, defined in `PEP 8`_. | |
placing them into the ``vars`` list, all while following the style | |
guidelines for Python code that are defined in `PEP 8`_. |
@@ -3,10 +3,10 @@ Data Transfer | |||
|
|||
Abstracted APIs should attempt to hide the implementation details of | |||
the remote or local API in a well organized data model. This data | |||
model should avoid returning raw JSON files, gRPC messages, SWIG objects, | |||
model should avoid returning raw JSON files, gRPC messages, `SWIG`_ objects, | |||
or .NET objects. It should preferably return standard Python objects |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or .NET objects. It should preferably return standard Python objects | |
and .NET objects. It should preferably return standard Python objects |
Consider the following code examples. The left-hand side shows the amount of | ||
work to start, establish a connection to, and submit an input file to MAPDL | ||
using auto-generated gRPC interface files. For more information, see | ||
`pyansys-protos-generator`_. The right-hand side shows the same workflow but | ||
uses the `PyMAPDL`_ library. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider the following code examples. The left-hand side shows the amount of | |
work to start, establish a connection to, and submit an input file to MAPDL | |
using auto-generated gRPC interface files. For more information, see | |
`pyansys-protos-generator`_. The right-hand side shows the same workflow but | |
uses the `PyMAPDL`_ library. | |
Consider the following code examples. The left side shows the amount of | |
work to start, establish a connection to, and submit an input file to MAPDL | |
using auto-generated gRPC interface files. For more information, see | |
`pyansys-protos-generator`_. The right side shows the same workflow but | |
uses the `PyMAPDL`_ library. |
@@ -1,15 +1,15 @@ | |||
Beyond PEP8 | |||
########### | |||
=========== | |||
This topic describes any delineations, clarifications, or additional procedures above and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This topic describes any delineations, clarifications, or additional procedures above and | |
This topic describes any delineations, clarifications, or additional procedures |
outlines deprecation best practices and a `Deprecation library <https://deprecation.readthedocs.io/>`_ | ||
already exists. However, there is no official guidance regarding deprecating features | ||
in an API within Python. This page seeks to clarify this issue and others. | ||
For example, `Stack Overflow Answer`_ outlines deprecation best practices and a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, `Stack Overflow Answer`_ outlines deprecation best practices and a | |
For example, `Stack Overflow Answer`_ outlines deprecation best practices, and a |
open-source nature of the project, documentation built by each PyAnsys library | ||
or project should be public and editable by users and the community at large. | ||
|
||
After following the documentation build strategy contained within both the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After following the documentation build strategy contained within both the | |
After following the documentation build strategy contained within both |
.. _pandas: https://pandas.pydata.org/ | ||
.. _pyvista: https://docs.pyvista.org/ | ||
.. _scipy: https://scipy.org/ | ||
.. _tensorflow: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this is empty?? @jorgepiloto
@jorgepiloto and @RobPasMue In draft PR #410, I moved all links with explicit target names to a central link file, I believe that we could close this PR.) |
Let's close it yeah - thanks @PipKat - I'll review that one =) |
Resolves #70.