DOC: Address occurrences of `pytensor-devs`

[larryshamalama]

Issue with current documentation:

There are several occurrences of pytensor-devs in our docstrings. This was probably due to #6365 and some instances were overlooked.

pymc/pymc/sampling/jax.py

Line 118 in 7b08fc1

# once https://github.com/pytensor-devs/pytensor/issues/637 is fixed.

pymc/pymc/logprob/rewriting.py

Line 421 in 7b08fc1

would. See https://github.com/pytensor-devs/aeppl/pull/78.

pymc/pymc/distributions/shape_utils.py

Line 410 in 7b08fc1

# specify_shape has a wrong signature https://github.com/pytensor-devs/pytensor/issues/1164

pymc/docs/source/learn/core_notebooks/pymc_pytensor.ipynb

Line 13 in 7b08fc1

"In this notebook we want to give an introduction of how PyMC models translate to PyTensor graphs. The purpose is not to give a detailed description of all [`pytensor`](https://github.com/pytensor-devs/pytensor)'s capabilities but rather focus on the main concepts to understand its connection with PyMC. For a more detailed description of the project please refer to the official documentation."

pymc/tests/sampling/test_jax.py

Line 137 in 7b08fc1

# be removed once https://github.com/pytensor-devs/pytensor/issues/637 is sorted.

pymc/tests/distributions/test_distribution.py

Line 695 in 7b08fc1

sys.platform == "win32", reason="https://github.com/pytensor-devs/pytensor/issues/871"

Idea or request for content:

All occurrences point to issues from Aesara and/or AePPL. The links should be rectified to the original issues that they refer to, unless we want to remove these altogether.

[jaharvey8]

I can probably take this one but I'm not 100% I totally follow. pytensor-devs should be changed to pymc-devs correct? But where do some of the referenced issues exist? For example, I can't find https://github.com/pytensor-devs/pytensor/issues/1164. Maybe the issue number changed when switching over to pymc-devs.

[ricardoV94]

Those issue exist on aesara-devs/aesara. When we forked we replaced the names aesara->pytensor but shouldn't have for the github links.

[larryshamalama]

I can probably take this one but I'm not 100% I totally follow. pytensor-devs should be changed to pymc-devs correct? But where do some of the referenced issues exist? For example, I can't find https://github.com/pytensor-devs/pytensor/issues/1164. Maybe the issue number changed when switching over to pymc-devs.

There is no such thing as "pytensor-devs", just "pymc-devs" as an organization. However, most issues were from the original Aesara and AePPL repositories. In other words, we can make the following substitutions in the comment hyperlinks:

• pytensor-devs/pytensor -> aesara-devs/aesara
• pytensor-devs/aeppl -> aesara-devs/aeppl

Feel free to open a PR and we can help you move forward with this!

[amyoshino]

Are you planning to work on this @jaharvey8?
If not I can open a PR for this issue :)

[jaharvey8]

Are you planning to work on this @jaharvey8? If not I can open a PR for this issue :)

If you have time in the near future, you should take it. I'm a little swamped the next week or so.