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

Fix compatibility with Python 3.10.0a4: fopen #344

Merged
merged 1 commit into from
Jan 6, 2021
Merged

Fix compatibility with Python 3.10.0a4: fopen #344

merged 1 commit into from
Jan 6, 2021

Conversation

vstinner
Copy link
Contributor

@vstinner vstinner commented Jan 6, 2021

Replace private _Py_fopen() with public fopen(): private _Py_fopen()
function was removed in 3.10.0a4:
https://bugs.python.org/issue32381

Replace private _Py_fopen() with public fopen(): private _Py_fopen()
function was removed in 3.10.0a4:
https://bugs.python.org/issue32381
@vstinner
Copy link
Contributor Author

vstinner commented Jan 6, 2021

Fedora downstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=1912903

@vstinner
Copy link
Contributor Author

vstinner commented Jan 6, 2021

If Boost needs a public C API for https://www.python.org/dev/peps/pep-0446/ please ask for it :-) But it would be a new Python feature. In general, third party projects should not rely on private functions, or be prepared for breakage at new Python version.

@stefanseefeld stefanseefeld merged commit cbd2d9f into boostorg:develop Jan 6, 2021
@stefanseefeld
Copy link
Member

Thanks !

@vstinner vstinner deleted the fopen branch January 6, 2021 21:02
gmloose pushed a commit to lofar-astron/PyBDSF that referenced this pull request Oct 31, 2022
And bump Boost version to fix removal of deprecated function:
boostorg/python#344
jakobandersen added a commit to jakobandersen/mod that referenced this pull request Nov 27, 2022
Due to boostorg/python#344 for Python 3.10
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.

None yet

2 participants