Add parameters to supply `./configure` cache files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, cli
Research direction
Start at the ./configure invocation and the command-line/environment argument handling. Trace how config.cache is selected for each Python 3.16 build, then verify that --configure-cache-file takes precedence over EVERY_PYTHON_CONFIGURE_CACHE_FILE and that invalid cache files produce the stated failure behavior. Done means repeated revisions can reuse a supplied cache file while users retain an easy CLI opt-out.
Written by the indexing model from the issue text.
Description
Say, --configure-cache-file and EVERY_PYTHON_CONFIGURE_CACHE_FILE.
This is mostly to speed up bisecting, where many first-seen revisions are built, and ./configure is currently being run for every single new revision without cache files. I also often find myself playing bingo with revisions, and most of the time the same config.cache would be fine. We're probably talking tens of seconds of difference.
If I have a fresh config.cache in any Python 3.16 directory, I can just supply that and it could be reused for most of the 3.16 revisions I'd want. It could happen that the cache is invalid, but then we could bail and let the user deal with it (then cli option would ideally take precedence over env var for an easy opt-out).
Would you be interested in a PR? :)
- Dominant language
- Python
- Stars
- 15
- Forks
- 3
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from savannahostrowski/every-python
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
savannahostrowski/every-python#72 · 1 comment ·
All issues in savannahostrowski/every-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100