3 fields are labelled "unnamed field" in `repr(scandir.DirEntry.stat())` about scandir HOT 3 OPEN

I believe the behaviour was introduced in #137. I don't (yet) know what a fix would look like, I'll update if I figure something out.

I happened to come across it while trying something similar for https://github.com/moreati/scanwalk (not ready for use by anyone, just a toy for now), specifically https://github.com/moreati/scanwalk/tree/franken-posixmodule

from scandir.

Thanks for the report. This is strange. Yeah, it's got to be due to #137, but I can't see how just changing that "unnamed field" string to const and renaming it could cause a behavioral difference. If this is important to you, feel free to dig in and come up with a fix. Would be interesting to see if this happens on Linux too.

I have limited time (and desire) to work on scandir these days, now that it's included in Python itself (has been since 3.5). Another approach would be to switch to using os.scandir directly (you may have to monkey-patch if it's a 3rd party library that's using scandir).

from scandir.

I've no pressing need for a fix, sorry for not making that clear. This report was mainly so people had a reference in case they hit it too. Thanks for shipping scandir all these years.

Confirm it also happens on Linux

(v) pi@rpi1:~/src $ python3 -c"import scandir; print(list(scandir.scandir('.'))[0].stat())"
scandir.stat_result(st_mode=16877, ..., unnamed field=1657451693, unnamed field=1657456796, unnamed field=1657456796)

from scandir.