python
Add import.complete audit event.
This adds a balancing "import.complete" audit event matching the existing "import" audit event, which allows the audit system to be used to observe programatically the same import timing information that is logged by PYTHONPROFILEIMPORTTIME.
The current import audit event may be fired twice for imports of native modules. The second import event can be distinguished from the first because the second argument is always non-None in this case, whereas it is always None in the first case.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
![bedevere-app[bot] avatar](https://avatars.githubusercontent.com/in/388350?v=4 "Published by a pub.dev verified publisher"){kind=small}
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
@zooba - Thomas Wouters suggested that you were a good person to tag on this change.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
@nineteendo I'm not sure what the convention is here. I'm happy to create an issue if that's preferred. I'm also aware that there should be a documentation change, which I've added (I hope; the convention for documenting audit events isn't totally clear - especially when they need additional text).
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
This needs a NEWS entry (just a basic Adds an ``import/module`` :ref:`auditing event <auditing>` message) and an issue (which I created for you). This is so it's possible to see from the changelog when it was introduced, and find links back to the PR.
