-
Notifications
You must be signed in to change notification settings - Fork 761
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
0.14 Release #1570
Comments
However, also none of these changes would be breaking, so I could just release 0.14 already? |
Note: #1626 (comment) - cross-compiling on |
@messense @birkenfeld I think we're very close now to a 0.14 release. This is what I still would like to see merged:
The remaining items I suggested in the OP are just documentation and bugfixes, which I think are good candidates to work on immediately after a release anyway. Anything else you folks think we should include? Would you be willing to review those outstanding PRs? Once they're merged I'll prepare a release branch and propose a date to put it live. |
The release is now live! |
I think the 0.14 release would be worth putting out soon. We've merged a lot of cleanups as well as a couple of new features. Also the updates to the
num
andhashbrown
dependencies will probably be useful for the downstream crates to have.This is what I propose we could merge before the 0.14 release goes live:
#[pyo3(name = "...")]
in pyfunction #1567 and some follow-up PRs to tidy up the attributes like#[name = "..."]
,#[text_signature = "..."]
to be a single#[pyo3(name = "...", text_signature = "...")]
. Also documentation Guide: #[pyo3(name = "")] and #[pyo3(from_py_with = "")] #1432#[pyproto]
can be a good thingThe text was updated successfully, but these errors were encountered: