-
-
Notifications
You must be signed in to change notification settings - Fork 32k
Add platform.invalidate_caches
for invalidating cached results
#122549
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
Labels
Comments
platform.invalidate_caches
for invalidating cached results (follow-up of #122525)platform.invalidate_caches
for invalidating cached results
Mostly out of curiosity - is there any way to watch for host name change? |
Well.. you could have a task that runs every second and checks whether the host name changed or not. |
vstinner
pushed a commit
that referenced
this issue
Nov 15, 2024
Allow to invalidate platform's cached results.
Completed in 612ac28. |
picnixz
added a commit
to picnixz/cpython
that referenced
this issue
Dec 8, 2024
Allow to invalidate platform's cached results.
ebonnal
pushed a commit
to ebonnal/cpython
that referenced
this issue
Jan 12, 2025
Allow to invalidate platform's cached results.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature or enhancement
Proposal:
In #122525, it was observed that many functions of the
platform
module use cached results. This is, in practice, preferrable, but it should also be possible, if needed, to invalidate cached results. One use case is when the host name changes (i.e., one of theuname()
components change).Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: