Skip to content

Conversation

@rickprice
Copy link

Fix problem where Windows returns different error codes than Unix does, and our Socked calls were only checking for Unix codes instead of Unix AND Windows codes.

There may be a better fix for this, but I need to talk to Jeremy.

These errors were probably caused by using a newer MSVC compiler.

Windows uses different error codes than Unix does, and our socket code
was only checking for Unix errors by number. This was causing some
things to fail that should have worked.

I believe that in the newer Python's that these errors are folded from
the Windows errors to Unix errors, but I can't find where to do that
here in Python2.
@rickprice rickprice requested a review from icanhasmath June 13, 2024 01:43
Copy link

@icanhasmath icanhasmath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix the extra spaces please.

@rickprice rickprice force-pushed the BE-3962-python-2-core-async branch from aba4248 to 115210b Compare June 19, 2024 02:20
@rickprice rickprice requested a review from icanhasmath June 21, 2024 21:40
Copy link

@icanhasmath icanhasmath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - we can look into reverting this if we can solve this issue globally.

@icanhasmath icanhasmath merged commit 7031989 into 2.7 Jun 21, 2024
@icanhasmath icanhasmath deleted the BE-3962-python-2-core-async branch June 21, 2024 21:55
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.

3 participants