Remove examples of time_imports nesting given it was a bug #46072
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As noted in #45861 (comment) the nested loading was a bug that #45861 fixed.
That means that the nesting in
@time_imports
is no longer seen, so this updates the docs. Also fixes up the changelog, which needs manual backport.Note that it means that the times shown are purely the import time of each package now (not the sum of all nested times), given that its deps are loaded further up the order.
So, previously, something like
Now:
(These timings haven't been tested on the same CSV & dep versions. They shouldn't be taken to mean there's a load speed improvement)