4d9d52d fixes macos, though 2.7 cannot be fixed due to package removal (Now how can I maintain my own projects...)

Thanks for this! What do you think about trying to fix 2.7 at the same time, by separating out 2.7 into a separate job and using this technique?

• python2.7 will be removed from the python-versions on June 19 actions/setup-python#672 (comment)
• scrool/xled@50c0da3

Does this (now fixed) bug affect Python 3.10.2?

@bschollnick sorry what bug?

Now c55be81 enforces extension.

https://github.com/benhoyt/scandir/actions/runs/5993519451/job/16254028573 had build failure but we did not notice without enforcing extension.

Now maybe it is better to exclude Windows pypy-2.7 from CI?

@benhoyt Addressed

The Mac OS reverting to python code, instead of the C code? I might of grabbed the wrong comment?

The Mac OS reverting to python code

we did not test if that even happened, though currently we can see it is using C.

please note that you should use pip.