Skip to content
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

Remove PYO3_NO_PYTHON hack for pyo3 >= 0.16.4 #875

Merged
merged 1 commit into from
Apr 16, 2022

Conversation

messense
Copy link
Member

@messense messense commented Apr 6, 2022

@netlify
Copy link

netlify bot commented Apr 6, 2022

Deploy Preview for maturin-guide ready!

Name Link
🔨 Latest commit 274b4fa
🔍 Latest deploy log https://app.netlify.com/sites/maturin-guide/deploys/62597ea338b1f7000887ce31
😎 Deploy Preview https://deploy-preview-875--maturin-guide.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@messense
Copy link
Member Author

messense commented Apr 6, 2022

@ravenexp Only the Docker tests failed now:

error: cannot set a minimum Python version 3.7 higher than the interpreter version 3.6 (the minimum Python version is implied by the abi3-py37 feature)

https://github.com/PyO3/maturin/runs/5847881580?check_suite_focus=true

@ravenexp
Copy link
Contributor

ravenexp commented Apr 6, 2022

I'm confused about where does Python 3.6 come from. pyo3 v0.16 only supports Python 3.7 and newer.

@messense
Copy link
Member Author

messense commented Apr 6, 2022

The default Python is 3.6 in that Docker image, but it shouldn't matter given that it's building an abi3 wheel?

@ravenexp
Copy link
Contributor

ravenexp commented Apr 6, 2022

PyO3 does not support setting minimum Python version for abi3 lower than 3.7 anymore.

Edit: I think the issue here is that unless PYO3_NO_PYTHON is set, the build script still tries to detect the host Python version, and refuses to use it when it's older than the minimum supported version.

@messense
Copy link
Member Author

messense commented Apr 7, 2022

I think the issue here is that unless PYO3_NO_PYTHON is set, the build script still tries to detect the host Python version, and refuses to use it when it's older than the minimum supported version.

Yeah, I don't think it makes sense for abi3 wheel on Unix now and on Windows once we integrate python3-dll-a.

@ravenexp
Copy link
Contributor

ravenexp commented Apr 7, 2022

Yeah, I don't think it makes sense for abi3 wheel on Unix now and on Windows once we integrate python3-dll-a.

This doesn't make much sense to me, but it's the long existing behavior someone may depend on.
It can be easily changed after PyO3/pyo3#2276 got merged, but this probably needs more discussion as a separate PyO3 issue.

@ravenexp
Copy link
Contributor

@ravenexp Only the Docker tests failed now:

error: cannot set a minimum Python version 3.7 higher than the interpreter version 3.6 (the minimum Python version is implied by the abi3-py37 feature)

https://github.com/PyO3/maturin/runs/5847881580?check_suite_focus=true

This should also work after upgrading pyo3 to 0.16.4

@messense messense force-pushed the rm-pyo3-no-python branch 2 times, most recently from 28336cf to 27923b8 Compare April 15, 2022 14:16
@messense messense changed the title Remove PYO3_NO_PYTHON hack Remove PYO3_NO_PYTHON hack for pyo3 >= 0.16.4 Apr 15, 2022
@messense messense force-pushed the rm-pyo3-no-python branch from 27923b8 to 274b4fa Compare April 15, 2022 14:18
@messense messense marked this pull request as ready for review April 15, 2022 14:22
@messense messense merged commit 4c08dbb into PyO3:main Apr 16, 2022
@messense messense deleted the rm-pyo3-no-python branch April 16, 2022 07:55
@messense messense linked an issue Apr 17, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better support for cross compiling to Windows
2 participants