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

gh-114917: fix typo post gh-114918 #131413

Merged
merged 1 commit into from
Mar 18, 2025
Merged

gh-114917: fix typo post gh-114918 #131413

merged 1 commit into from
Mar 18, 2025

Conversation

maxbachmann
Copy link
Contributor

@maxbachmann maxbachmann commented Mar 18, 2025

@vstinner when taking the patch from here back to our code base I noticed that apparently I made a typo along the way 😓

@picnixz picnixz changed the title fix typo gh-114917: fix typo post gh-114918 Mar 18, 2025
@picnixz picnixz requested a review from vstinner March 18, 2025 12:40
Copy link
Member

@picnixz picnixz left a comment

Choose a reason for hiding this comment

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

I'm surprised that it wasn't detected by the compiler, but I think we don't test this part of the code? because AFAICT, ai is not a pointer.

@maxbachmann
Copy link
Contributor Author

we don't even compile it because it's conditionally including the c file

@picnixz
Copy link
Member

picnixz commented Mar 18, 2025

Yes, but shouldn't we have some coverage for such code then? at least from the CI perspective

@maxbachmann
Copy link
Contributor Author

maxbachmann commented Mar 18, 2025

I guess optimally we would. This would require a separate test / build target though where we enforce that the fallback implementation is used.

Edit: If that's something we want I can open a separate issue for that. From my perspective we should:

  • add a build where we force HAVE_GETADDRINFO and HAVE_GETNAMEINFO to false
  • run tests with it (possibly just the socket module tests to save time)

@vstinner vstinner merged commit 49234c0 into python:main Mar 18, 2025
45 checks passed
@vstinner
Copy link
Member

Merged. Well, it happens with code which is not tested by our CIs.

@picnixz
Copy link
Member

picnixz commented Mar 18, 2025

I would say it's always good to add coverage for something that we use as a fallback implementation. However, I don't know how frequent it is to use the fallback implementation. I don't know how hard it will be to write such tests, but we should at least test that the file compiles (namely, we should at least have a build bot that we can test the implementation on).

@vstinner
Copy link
Member

These changes are to support PlayStation platform: #114918 (comment)

PlayStation is not supported by PEP 11. I don't think that it's worth it to spend more time on this issue, it's now solved.

colesbury pushed a commit to colesbury/cpython that referenced this pull request Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants