Local dev: cache PyPI responses for one hour #164
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.
This helps local development. For the daily deploy, it won't matter, because the CI is a fresh environment and won't have the cache file (the 1-hour cache would have expired anyway).
It speeds up repeated runs from ~9 seconds to ~1 second.
First run:
Second run:
Delete
requests-cache.sqlite
to get a fresh batch.Also add
--number
togenerate.py
for testing, in case you only want to fetch a few.Finally, remove an unused import, and use
math.tau
directly (added in 3.6) instead of calculating2 * math.pi
.