-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
bpo-37221: Add PyCode_NewWithPosOnlyArgs to be used internally and set PyCode_New as a compatibility wrapper #13959
Conversation
I would prefer to call the new function PyCode_NewWithPosArgs() rather than PyCode_NewEx(). |
Would it make sense to wait to merge this PR just before next beta2, and also synchronize with Cython to make sure that Cython will be compatibl with Python 3.8 beta2, soon after beta2 is released? |
I renamed the new function to |
We can merge and backport it and it will be released before in beta2, right? I will do the PR for Cython right away. They can chose to merge it when they think is better. |
Misc/NEWS.d/next/C API/2019-06-11-02-50-38.bpo-37221.4tClQT.rst
Outdated
Show resolved
Hide resolved
When you're done making the requested changes, leave the comment: |
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.
LGTM, but I would prefer a second review. @methane, @serhiy-storchaka, @ncoghlan, @encukou, anyone?
Misc/NEWS.d/next/C API/2019-06-11-02-50-38.bpo-37221.4tClQT.rst
Outdated
Show resolved
Hide resolved
Yes, please. Otherwise, we will loose a month of CI time during which Cython cannot adapt (because the CPython API version does not change before the release) and during which users cannot properly test with the unreleased CPython master because Cython does not work on it any more. |
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.
Please add a What's New entry.
Would be nice if Cython release a new version which will use a special case only for Python |
@serhiy-storchaka There is already a what's new entry. Do you mean something extra or something different? |
Sorry, I missed it. |
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 @pablogsal
@serhiy-storchaka The issue for Cython is that the 3.8 dev branch is currently still mostly advertising itself as 3.8b1: https://github.com/python/cpython/blob/3.8/Include/patchlevel.h @ambv Could we do something a little odd here, and change the branch version string to be "3.8b2-" and bump the release serial to "2" before the actual release? That way the change could be merged, and Cython would be able to correctly detect it as being a different build from 3.8b1. |
change the branch version string
Note that the dependency is in the generated C code and based on PY_VERSION_HEX, which cannot easily be modified in this way.
|
I have rebased to fix the merge conflicts. |
Sorry, missed the notification on this one. I'd rather not, let's just merge this shortly before beta2, say: Friday. |
I read that as an invitation for anyone to hit the green button on Friday. Let us know if you want to do the merge yourself. |
Thanks @pablogsal for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
GH-14505 is a backport of this pull request to the 3.8 branch. |
…t PyCode_New as a compatibility wrapper (pythonGH-13959) Add PyCode_NewEx to be used internally and set PyCode_New as a compatibility wrapper (cherry picked from commit 4a2edc3) Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
FYI, Cython 0.29.11 has been released with the necessary change for beta-2. |
That's great! Thank you. |
…t PyCode_New as a compatibility wrapper (pythonGH-13959) Add PyCode_NewEx to be used internally and set PyCode_New as a compatibility wrapper
…t PyCode_New as a compatibility wrapper (pythonGH-13959) Add PyCode_NewEx to be used internally and set PyCode_New as a compatibility wrapper
Fixes the follwoing error: "TypeError: code() takes at least 14 arguments (13 given)". The cause of the issue is a breaking change in CodeType constructor in Python 3.8. https://bugs.python.org/issue37221 This should have been fixed by python/cpython#13959 and python/cpython#14505, but the code still fails.
* SDK - Fix SDK on Python 3.8 Fixes the follwoing error: "TypeError: code() takes at least 14 arguments (13 given)". The cause of the issue is a breaking change in CodeType constructor in Python 3.8. https://bugs.python.org/issue37221 This should have been fixed by python/cpython#13959 and python/cpython#14505, but the code still fails. * Simplified the replace call
* SDK - Fix SDK on Python 3.8 Fixes the follwoing error: "TypeError: code() takes at least 14 arguments (13 given)". The cause of the issue is a breaking change in CodeType constructor in Python 3.8. https://bugs.python.org/issue37221 This should have been fixed by python/cpython#13959 and python/cpython#14505, but the code still fails. * Simplified the replace call
https://bugs.python.org/issue37221