This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients serhiy.storchaka, steve.dower, xtreak
Date 2019-09-13.11:44:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> when added sys.audit() for glob.glob(), should not it be added for Path.glob() too? And for os.walk()?

Sure, those would make sense.

They all go via scandir() which has its own event too (and will do for each directory), but being able to see that it came from a glob or walk call could be useful information.

Maybe moving the sys.audit call in glob.glob further down in the function would avoid some of the recursion? I don't want to duplicate where it's raised too much, as that provides opportunities to bypass it, but this one is only slightly informative - os.scandir is the real one that you'd worry about seeing.
Date User Action Args
2019-09-13 11:44:29steve.dowersetrecipients: + steve.dower, serhiy.storchaka, xtreak
2019-09-13 11:44:29steve.dowersetmessageid: <>
2019-09-13 11:44:29steve.dowerlinkissue38149 messages
2019-09-13 11:44:29steve.dowercreate