Holmanb/python3.13

[holmanb]

Proposed Commit Message

ci: Add Python 3.13

[TheRealFalcon]

Should we close this PR and re-open when the run can work?

[holmanb]

Should we close this PR and re-open when the run can work?

Or maybe the opposite - we open if failing, so that we can easily check in periodically to see if it is failing because of test failures or still failing because of build failures. WDYT?

[TheRealFalcon]

Keeping it with a non-vote to CI is good

[TheRealFalcon]

non-vote

Reading about it...is this even an option? It's looks like it's not implemented. actions/runner#2347

[github-actions]

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging TheRealFalcon, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag TheRealFalcon to reopen it.)

[holmanb]

Requires #4669

[TheRealFalcon]

Will this fail CI if the dev job fails?

[holmanb]

Will this fail CI if the dev job fails?

Yep, over 1000 reactions to the top comment and Github still hasn't bothered to implement this.

We can let this grow stale until 3.13 is released, if you want, but we had 3.12 as a job before it was released and didn't have any troubles, so alternatively we could just drop 3.13 if it causes troubles. I got a passing run on 3.13, so I'm happy either way.

[TheRealFalcon]

alternatively we could just drop 3.13 if it causes troubles

Yeah, I think this makes more sense. Better to get the signal if we need it rather than ignore it due to possible breaking changes from Python, which seem pretty unlikely.