| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
The current implementation doesn’t seem useful to me.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. The function looks useful when the hostname changes, tests look complete, and the documentation is good enough.
Sorry, something went wrong.
|
I just want to be sure that build bots won't be unhappy with this change for whatever reason (we'll get the answer in roughly 8 hours) |
Sorry, something went wrong.
Sorry, something went wrong.
| This is typically useful when the platform's :func:`node` is changed | ||
| by an external process and one needs to retrieve the updated value. | ||
|
|
||
| .. versionadded:: 3.14 |
There was a problem hiding this comment.
I should have used a versionadded:: next here but at that time, it didn't exist yet. Not sure if this warrants an additional commit though. WDYT @vstinner
Sorry, something went wrong.
There was a problem hiding this comment.
next will be replaced with 3.14 anyway, there is no need to replace it.
Sorry, something went wrong.
There was a problem hiding this comment.
Yea but sometimes users are confused that the feature is present in the docs but not in the current release. That was the purpose of next
Sorry, something went wrong.
Allow to invalidate platform's cached results.
Allow to invalidate platform's cached results.
| Back | FazBrowse Home | New Git URL |
Using a cache invalidation approach is probably better than querying the new results every time. At least, it will not cause any breaking change.
📚 Documentation preview 📚: https://cpython-previews--122547.org.readthedocs.build/