Skip to content

Port NBs from PyMC3 to PyMC #236

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

Closed
OriolAbril opened this issue Oct 3, 2021 · 3 comments
Closed

Port NBs from PyMC3 to PyMC #236

OriolAbril opened this issue Oct 3, 2021 · 3 comments

Comments

@OriolAbril
Copy link
Member

OriolAbril commented Oct 3, 2021

URGENT: Update all references to the style guide. The style guide has been renamed so the link now needs to be updated from all the places where it used to be present as they are now broken. For example the one in https://github.com/pymc-devs/pymc-examples/blob/main/CONTRIBUTING.md#pull-request-checklist

Change all occurrences of PyMC3 to PyMC. IMPORTANT The change should happen as the notebooks are updated to use v4. Until the beta release is out, notebooks should still use PYMC3 name and use 3.11.x version as they will still be part of the pymc3 docs at https://pymc.readthedocs.io/en/v3.11.4/

side note, feel free to split in two different issues.

cc @martinacantaro @canyon289

@canyon289 canyon289 changed the title Renaming Renaming PyMC3 to PyMC Oct 3, 2021
@twiecki twiecki changed the title Renaming PyMC3 to PyMC Port NBs from PyMC3 to PyMC May 30, 2022
@twiecki
Copy link
Member

twiecki commented May 30, 2022

@OriolAbril Can we uncouple upgrading the NBs to v4 and updating them to the new style guide? With the gallery they should still be accessible so I don't think it's a hard requirement. I think most NBs can be upgraded automatically with https://github.com/pymc-devs/pymc-examples/blob/main/scripts/rerun.py that way and users can find correctly versioned docs.

@drbenvincent
Copy link
Contributor

Now we've released v4, the urgency of this has diminished. So we could close this issue and fall back to #333?

@twiecki
Copy link
Member

twiecki commented Sep 14, 2022

Closing in favor of #333.

@twiecki twiecki closed this as completed Sep 14, 2022
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

No branches or pull requests

3 participants