-
Notifications
You must be signed in to change notification settings - Fork 101
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
Fix compilation bug in toolchain >= 1.70.0 #322
Conversation
1bc73f1
to
bf88283
Compare
I think the mypy error is occured out of my code, but I don't know why it fails while the |
Are you sure this is an intentional change? I don't see it mentioned in https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md |
Actually I cannot figure out which change on rustc break the compatibility. Recently --crate-type option is implemented in cargo, so I think it is safer to use --crate-type option on cargo. |
@davidhewitt I think the mypy error is not related on this PR, so is it good for you to fix it in the same branch? |
Yes, I can fix the mypy error separately. Argument for using cargo options seems reasonable to me. It looks like We can then document this in the CHANGELOG as "changed" rather than "fixed". |
Thanks a lot. I fixed the version and modified CHANGELOG. |
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.
Thanks - I'll try to tidy things up on main
with a view to releasing tomorrow.
## 1.6.0 (2023-04-27) ### Changed - Prefer passing `--crate-type` option to cargo if "toolchain >= 1.64". [#322](PyO3/setuptools-rust#322) ### Fixed - Fix a bug where rebuilding the library would cause any running processes using it to segfault. [#295](PyO3/setuptools-rust#295) - Fix `setup.cfg` format for compatibility with "poetry==1.4.0". [#319](PyO3/setuptools-rust#319)
Fix #320
Please see the discussion in #321