GeezerVison

The following commit authors need to sign the Contributor License Agreement:

• [email protected]

Click the button to sign:

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

@VictorNorman, please sign the CLA.

@VictorNorman, please sign the CLA.

Quoting https://devguide.python.org/committing/#assessing-a-pull-request:

Make sure that the contributor has signed a Contributor Licensing Agreement (CLA), unless their change has no possible intellectual property associated with it (e.g. fixing a spelling mistake in documentation)

AFAICS, this PR can land without the CLA being signed.

Quoting https://devguide.python.org/committing/#assessing-a-pull-request:

Make sure that the contributor has signed a Contributor Licensing Agreement (CLA), unless their change has no possible intellectual property associated with it (e.g. fixing a spelling mistake in documentation)

AFAICS, this PR can land without the CLA being signed.

Darn, that does not help; I'm unable to merge since the CI does not pass. So, @VictorNorman, please sign the CLA, or I cannot merge this.

I'm unable to merge since the CI does not pass

This seems to be a regression with the new CLA system - was it intended? @VictorNorman has an institutional email address, so may need to go through the corporate signing process with his university, rather than the individual process.

A

I'm not sure what to do with this PR. Should we just close it? As long as Victor Norman does not respond, there is not much I can do, at least.

@erlend-aasland it isn't a copyrightable change, so I would close and you could just push the changes & backport as a core dev (I would open a PR myself but I'm plagued by CLA issues!)

A

Ok, thanks, I'll do that tomorrow.