A5rocks

For some reason just adding 3.13 to CI fails -- I tried yesterday. But yeah that's tracked in a separate issue (the general CI improvements one)

I'm struggling to reconcile: ``` _epoll = attr.ib(factory=select.epoll) ^^^^^^^^^^^^ AttributeError: module 'select' has no attribute 'epoll' ``` And yet `getattr(select, "epoll", None)` seems to work... (I don't have anything productive...

Oh huh I see the problem now. I think a solution would be to use a lambda and reference select.epoll inside (assuming you don't actually end up using trio?) But...

Surprised at the loss of 3 percentage points of coverage -- is there some platform where things broke? ... interesting: https://github.com/python-trio/trio/actions/runs/7865327122/job/21458126980?pr=2951#step:7:12 (edit: reported to https://github.com/codecov/codecov-action/issues/1279)

Is codecov just consistently reporting less coverage? It looks like -3% coverage on all platforms. It looks like codecov is regenerating `coverage.xml` rather than using the one we made (which...

I tried a workaround and it didn't work. I'm not entirely sure my hypothesis on why this is taking away coverage is correct. But nonetheless consider me displeased that somehow...

~~Do you mind if this issue gets transferred over to the `trio` repository now that that has inline type hints?~~ I'll just do it, feel free to transfer this back...

Probably similar to what you did for the `dir` thing!

Sorry, I just misread https://github.com/python-trio/trio/pull/2864/commits/a0f58eaffbe46636716beea8b6f887dafc4e8a72

It's easy enough to disable but I'm not sure if we want to try doing any deeper analysis first.