Skip to content

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

Merged
merged 7 commits into from
Feb 4, 2022
Merged

Conversation

michaelosthege
Copy link
Member

This PR makes some simple backports to reduce API breakage in the v3v4 transition.

@michaelosthege michaelosthege added this to the v3.11.5 (vNext) milestone Jan 25, 2022
@michaelosthege michaelosthege self-assigned this Jan 25, 2022
@michaelosthege michaelosthege changed the title Backwards-compatible rename LognormalLogNormal API backports and deprecation warnings Jan 25, 2022
@michaelosthege michaelosthege marked this pull request as ready for review January 27, 2022 08:10
Copy link
Member

@OriolAbril OriolAbril left a 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)).
Copy link
Member

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
Copy link
Member

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

Copy link
Member Author

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.

@michaelosthege
Copy link
Member Author

@OriolAbril can we merge this?

@OriolAbril OriolAbril merged commit baec0c3 into v3 Feb 4, 2022
@OriolAbril OriolAbril deleted the backport-lognormal-alias branch February 4, 2022 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants