Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf: Call update_env only once per Markdown instance #201

Merged
merged 1 commit into from
Dec 28, 2020

Conversation

oprypin
Copy link
Member

@oprypin oprypin commented Dec 26, 2020

The follow-up calls for each block make no difference at all, and are getting quite expensive.

The follow-up calls for each block make no difference at all, and are getting quite expensive.
@pawamoy pawamoy merged commit 8c16159 into mkdocstrings:master Dec 28, 2020
@pawamoy
Copy link
Member

pawamoy commented Dec 28, 2020

Easy change for improved perfs, merging! Thanks @oprypin!

jdpatt added a commit to jdpatt/mkdocstrings that referenced this pull request Jan 6, 2023
Instead of a boolean of has any env been updated, track by handle name
which env has been updated.

References: mkdocstrings#201
Fixes: 502
jdpatt added a commit to jdpatt/mkdocstrings that referenced this pull request Jan 9, 2023
Instead of a boolean of has any env been updated, track by handle name
which env has been updated.

References: mkdocstrings#201
Fixes: 502
pawamoy pushed a commit that referenced this pull request Jan 11, 2023
Instead of using a single boolean,
record which handler's env has been update with a set.

PR #201: #201
Issue #502: #502
PR #507: #507
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants