Repository navigation
Missing dependency on Include/cpython/frameobject.h #85646
Description
Activity
When Include/cpython/frameobject.h was created, there was no dependency added to Makefile.pre.in.
- added3.10 (EOL)end of lifeend of lifebuildThe build process and cross-buildThe build process and cross-build
on Aug 4, 2020 Created a pull request. Hopefully I didn't muff the protocol too badly.
Created a pull request. Hopefully I didn't muff the protocol too badly.
Your PR has 124 commits, that looks strange.
Your PR has 124 commits, that looks strange.
Funny, it told me just one file had changed (Makefile.pre.in). I was attempting to make a PR against that one change from my fork of master to the main repo. Let me take another crack at it.
I see what @vstinner is talking about. If you look at those commit messages, they all look to be of the form "Merge remote-tracking branch 'upstream/master'". That is, they are me syncing python/cpython/master to python/smontanaro/master. There is, in fact, just the one file changed, Makefile.pre.in, with the addition of a single dependency.
I don't know how to get rid of all those commit messages.
they all look to be of the form "Merge remote-tracking branch 'upstream/master'".
Aside from one where I erroneously committed a change to the wrong
branch, then backed it out immediately.I don't know how to get rid of all those commit messages.
I suggest you to create a local branch per change, rather than using "master".
I consider that "origin" is git@github.com:python/cpython.git. Check your remotes with "git remote -v".
Example where "master" is your PR 21732.
git switch -c frameobject master
git switch master
git reset --hard origin/master # revert your changesThen fix your frameobject:
git switch master
git fetch && git merge --ff # ensure that you are up to date
git switch frameobject
git rebase masterCheck what you get:
git log master.. --pretty=oneline
You should see only one commit.
Close your PR and create a new one on the "frameobject" branch.
> I don't know how to get rid of all those commit messages.
I suggest you to create a local branch per change, rather than using "master".
I consider that "origin" is git@github.com:python/cpython.git. Check your remotes with "git remote -v".
Hmmm... Seems like a bunch of extra work for a one-line change to a
Makefile... There's no easier way to create PRs for these trivial
changes?Sorry to rain on your parade, but couldn’t this be a new package on PyPI?
Wrong issue, sorry. (Bpo bug?)
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields: