Why the merged PR's status is `closed` in bpo


I found that the merged PR 15386’s status is closed in bpo27961.

is this behavior within our plan?

As noted in the devguide, that’s the correct status for an issue, whose PR was merged. You can verify that it is fixed through the Resolution field.

I think @shihai1991 was referring to the status of the PR in bpo, where it was expected for it to say “merged” instead of “closed”

I’m not familiar with how bpo works. Perhaps Ezio has more context.

1 Like

Oh okay, I thought @shihai1991 was referring to the whole issue. Sorry about that!

Hmm, interesting. I have yet to see this issue before.

To verify that it wasn’t an issue with GitHub, I used a GraphQL query against the v4 API (https://developer.github.com/v4/explorer/):

query { 
  repository(name: "cpython", owner: "python") { 
    pullRequest(number: 15386) {

This returned the following results:

  "data": {
    "repository": {
      "pullRequest": {
        "state": "MERGED"

So it seems that it’s likely an issue with the roundup script that extracts data from the GitHub API. I’m not knowledgeable about the implementation details of it, so I’m not sure what would have caused the issue.

Does anyone know where the code for the roundup extraction script is contained? I seem to recall that some other bpo scripts were hosted on BitBucket, but I’m not sure where the repository is or if it’s even public.

I believe the sourcecode for bpo is at https://bitbucket.org/python/tracker-cpython/

1 Like

FYI, I manually set the BPO PR status back to “merged”.


OK, this is core developer’s power.

Looks we need check the sourcecode of bpo as @Mariatta said if we have free time :wink: