Br. do you feel that? That's the chill of *beta freeze* coming
closer. Meanwhile, your friendly CPython release team doesn’t
rest even on holidays and we have prepared a shiny new release for you:
Python 3.10.0a7.
Dear fellow core
I don't have much to add (this occurs to me too and I just bulk-delete the
messages) but I wonder if the problem might be caused by a situation where
GitHub doesn't realize that a repo is a fork of cpython? I suppose that
could happen if someone creates a fresh repo and pushes a local clone of
On Tue, Apr 6, 2021 at 6:41 PM Pablo Galindo Salgado
wrote:
> I think this is a good motivation to use
> https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
> instead as you can write your own commit message there and schedule the
Steve Dower's workflow is to use git merge origin/master, and he did that
earlier today, causing the most recent flurry. His repo is a fork of
cpython but its master branch is 1000s of commits behind, so probably
there's some bug in GitHub where the commits being merged are seen as new.
Mariatta,
Hi,
About this very specific ABI issue, one long term solution would be to
exclude the PyThreadState structure from the C API, to not rely on it
the ABI level.
I started to add getter functions in Python 3.9:
PyThreadState_GetInterpreter(), PyThreadState_GetFrame() and
PyThreadState_GetID(). I'm
Hi,
I'm getting more and more email notifications when a commit contains
my GitHub handle ("@vstinner"). For example: "Automerge-Triggered-By:
@vstinner".
The issue is that it's not only commits from the python/cpython GitHub
project, but also on all forks of the python project. Example:
On Tue, Apr 6, 2021 at 9:36 AM Victor Stinner wrote:
> I'm getting more and more email notifications when a commit contains
> my GitHub handle ("@vstinner"). For example: "Automerge-Triggered-By:
> @vstinner".
Yes, this is a pretty substantial failing of GitHub for popular projects :(
> But the
I think the real solution to this should come from Github if we can
convince them that it's worth their time to have a separate notification
category for these things. One short-term solution for this might be to
modify the commit messages that automerge uses. The simplest version of
this would be
> P.S. If anyone with communications channels to Github is planning to lobby
> for changes, I'd prefer a way to say, "Never notify me of @ messages in
> commit messages" followed by a special CC: address for easy filtering,
> followed by "Please don't notify me a second time when an identical
> This is one of the several reasons that I don't like using the PR
description as the commit message when using auto-merge :).
I think this is a good motivation to use
https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
instead as
10 matches
Mail list logo
