-
Notifications
You must be signed in to change notification settings - Fork 4.1k
THRIFT-5899: Python tests fail for the Appveyor MSVC builds #3229
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
Conversation
- See THRIFT-5898
- PR#2929 called out that the changes breaks Python 3.5 since types came in in 3.6 - Python 3.6 errors out with 'from __future__ import annotations' since it looks like it was only added in 3.7
- Getting `raise TApplicationException(TApplicationException.MISSING_RESULT, "testEnum failed: unknown result"` error - PR#2825 state it is a breaking change, not sure why and for what version of Python
- Appveyor error: ` AttributeError: module 'ssl' has no attribute 'PROTOCOL_TLS_CLIENT'`
|
I have just logged https://issues.apache.org/jira/browse/THRIFT-5900, will try to see if I can do something to get past it without trying to upgrade python. Don't want to now have to mix this PR with also upgrading to Python 3.14 |
d804449 to
b0e704b
Compare
|
@fishy Thanks for your inputs and review, I think I have addressed all feedback. I think we can merge, I propose leaving the |
|
@CJCombrink thank you! |
|
Given that there is now an expectation for the appveryor builds to pass is there a way to put more strict check on it not getting broken again by PRs to prevent this type of regressions in future? |
Fix issues as picked up by the MSVC build
Note: The disabling of the shared lib is done due to THRIFT-5898 and should be fixed by #3226 whereby the build will be changed again
[skip ci]anywhere in the commit message to free up build resources.