-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
pin pymc==5.14 #162
pin pymc==5.14 #162
Conversation
We pinned the versions precisely because of the frecuent releases. A common scenario is that pymc-bart import fails due to a sudden change in a module name or function. It is possible to automatically run tests for every new pymc/arviz release? |
Ahh ok! I don't think I know about doing this automatically. I'll close this one and open another one for the upgrade to 5.14 😄 |
Shall we still upgrade to the latest version? 5d7fff1 |
Updating makes sense. |
As we have new releases (https://github.com/pymc-devs/pymc/releases) regularly, I suggest we unpin the exact versions of PyMC and Arviz :)I changed the scope and just pinned the latest version.
I also removed the pre-commit restrictions as they are not necessary