python / python/miss-islington
Backport fails without any output
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 116
- Forks
- 43
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I tried to trigger backporting https://github.com/python/cpython/pull/114558 to 3.12 several times. Every time @miss-islington reports that it starts working, but do not produce any output.
Backporting to 3.11 failed due to conflicts, and this was reported.
It successfully creates backports to 3.12 for other PRs.
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.
Research direction
Reproduce the 3.12 backport request for CPython PR 114558, then compare its handling and reporting with the known 3.11 conflict case. Done means a failed or silent 3.12 attempt produces useful output while successful 3.12 backports remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100