Add Winloop to test suite if User is using Windows

[Vizonex]

What do these changes do?

Felt that winloop should be added because I made it for supporting uvloop on windows operating systems.

Are there changes in behavior for the user?

Adds winloop to the test-suite which should hopefully allow me and other maintainers to fix more bugs in the future.

Is it a substantial burden for the maintainers to support this?

Really it shouldn't be too much of a burden to maintain this new addition since If it's winloop's fault you can always throw the issue on our github. I'm also looking for maintainers with my current project so that it will outlive the time I have planned to spend maintaining it, currently I am the only active maintainer since the other maintainer we had seems to have gone silent since our last release.

Related issue number

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES/ folder

  • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

  • if you don't have an issue number, change it to the pull request
    number after creating the PR

    • .bugfix: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    • .feature: A new behavior, public APIs. That sort of stuff.
    • .deprecation: A declaration of future API removals and breaking
      changes in behavior.
    • .breaking: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    • .doc: Notable updates to the documentation structure or build
      process.
    • .packaging: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    • .contrib: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    • .misc: Changes that are hard to assign to any of the above
      categories.

  • Make sure to use full sentences with correct case and punctuation,
    for example:

    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.

[Vizonex]

Please Know that I do not wish to give my real name in the contributors list for my own safety.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.75%. Comparing base (b58c3ad) to head (451d80e).
Report is 6 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10922   +/-   ##
=======================================
  Coverage   98.75%   98.75%           
=======================================
  Files         129      129           
  Lines       39072    39097   +25     
  Branches     2164     2167    +3     
=======================================
+ Hits        38586    38611   +25     
  Misses        337      337           
  Partials      149      149           

Flag	Coverage Δ
CI-GHA	98.63% <66.66%> (-0.01%)	⬇️
OS-Linux	98.34% <33.33%> (-0.01%)	⬇️
OS-Windows	96.49% <33.33%> (-0.02%)	⬇️
OS-macOS	97.49% <33.33%> (-0.01%)	⬇️
Py-3.10.11	97.38% <66.66%> (-0.01%)	⬇️
Py-3.10.17	97.92% <33.33%> (-0.01%)	⬇️
Py-3.11.12	97.99% <33.33%> (-0.02%)	⬇️
Py-3.11.9	97.46% <66.66%> (-0.02%)	⬇️
Py-3.12.10	98.41% <66.66%> (-0.01%)	⬇️
Py-3.13.3	98.39% <66.66%> (-0.01%)	⬇️
Py-3.9.13	97.25% <66.66%> (-0.01%)	⬇️
Py-3.9.22	97.78% <33.33%> (-0.01%)	⬇️
Py-pypy7.3.16	84.37% <33.33%> (-8.58%)	⬇️
VM-macos	97.49% <33.33%> (-0.01%)	⬇️
VM-ubuntu	98.34% <33.33%> (-0.01%)	⬇️
VM-windows	96.49% <33.33%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codspeed-hq]

CodSpeed Performance Report

Merging #10922 will not alter performance

_{Comparing Vizonex:add-winloop-to-testsuite-if-using-windows (451d80e) with master (19643c9)}

Summary

✅ 59 untouched benchmarks

[bdraco]

Please add a contrib changelog note.

Thanks!

[Vizonex]

Please add a contrib changelog note.

Thanks!

@bdraco Thanks for the feedback, Added :)

[bdraco]

You'll need to update requirements/base.in as well

[Vizonex]

You'll need to update requirements/base.in as well

Alright. Give me a few seconds to do this 👍

[Vizonex]

should work let me know if "cpython" should or shouldn't be recommended.

[bdraco]

Looks like the ci doesn't like testsuite as a single word.

You will need to add winloop to the docs spelling word list to get that one to pass

[Vizonex]

Looks like the ci doesn't like testsuite as a single word.

You will need to add winloop to the docs spelling word list to get that one to pass

Shouldn't be too bad how should I approach changing it?

[bdraco]

Looks like the ci doesn't like testsuite as a single word.
You will need to add winloop to the docs spelling word list to get that one to pass

Shouldn't be too bad how should I approach changing it?

Add winloop into docs/spelling_wordlist.txt at the right lexicographic order

[Vizonex]

@bdraco Thanks for your help :)

[Vizonex]

@bdraco Seems the workflow passed successfully is there anything else I should do?

[bdraco]

I'll check it again after some sleep

[patchback]

Backport to 3.12: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.12/5fac5f1988d294ab811318face9dda67602bb923/pr-10922

Backported as #10930

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[bdraco]

Thanks @Vizonex

[Vizonex]

Thanks @Vizonex

Your welcome glad I could be able to contribute, I have some very unique plans to make aiohttp better in the future and this was just the start.