feat: rc support#231
Conversation
ofek
left a comment
There was a problem hiding this comment.
Thanks! Let's try running it to see the generated output.
The generated output is exactly the same as running it without my change, as there are currently no rcs active. I ran it with betas and rcs though to demonstrate, which
|
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b1b6aa21a9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| response = httpx.get(RELEASES_URL, headers=headers, timeout=60, params={'page': page, 'per_page': 5}) | ||
| progress = Progress() | ||
| task = progress.add_task("Updating distributions...") | ||
| progress.start() |
There was a problem hiding this comment.
Stop the manually started progress display
Starting Progress manually without a matching stop() leaves Rich's live display active when the generator finishes or raises, so running this script in an interactive terminal can leave the cursor hidden and terminal rendering state unrestored. Wrap the pagination loop in a with Progress() as progress: block or stop it in a finally clause.
Useful? React with 👍 / 👎.
Doesn’t in any way discriminate the RCs, they just pop up in the list.
Testing by changing
!= 'rc'tonot in {'rc', 'b'}, I noticed that only for 3.15, betas popped up. Do they delete beta assets from old releases?Fixes #232