-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
API backports and deprecation warnings #5389
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
Conversation
Lognormal
→LogNormal
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.
Might have missed it but I don't see the new name in the docs, it should be added to the api/distributions/continuous file
@@ -5,6 +5,7 @@ | |||
+ The `pm.logp(rv, x)` syntax is now available and recommended to make your model code `v4`-ready. Note that this backport is just an alias and much less capable than what's available with `pymc >=4` (see [#5083](https://github.com/pymc-devs/pymc/pulls/5083)). | |||
+ The `pm.Distribution(testval=...)` kwarg was deprecated and will be replaced by `pm.Distribution(initval=...)`in `pymc >=4` (see [#5226](https://github.com/pymc-devs/pymc/pulls/5226)). | |||
+ The `pm.sample(start=...)` kwarg was deprecated and will be replaced by `pm.sample(initvals=...)`in `pymc >=4` (see [#5226](https://github.com/pymc-devs/pymc/pulls/5226)). | |||
+ `pm.Lognormal` is now available as an alias for `pm.Lognormal` (see [#5389](https://github.com/pymc-devs/pymc/pull/5389)). |
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.
Capitalization is wrong, I think the first one should be LogNormal
@@ -9,7 +9,7 @@ dependencies: | |||
- mkl-service | |||
- nbsphinx>=0.4 | |||
- numpy=1.15 | |||
- numpydoc>=0.9 | |||
- numpydoc<1.2 |
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.
Would using numpydoc! =1.2.0 allow installation of 1.2.1? The PR fix was merged today, the patch release should hopefully not take long, and with that we could forget about the pin completely
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.
While they labeled it 1.2.0
on GitHub, the PyPI release is just 1.2
, so I'm not sure if !=1.2.0
would work.
Also we have the <1.2
on main
already.
But I'm now "watching" the numpydoc repo and will get a notification 🔔 when they do the next release.
@OriolAbril can we merge this? |
This PR makes some simple backports to reduce API breakage in the
v3
→v4
transition.