On Tue, 14 Sep 2021 22:30:24 +0200 Paul Gevers <elb...@debian.org> wrote: > Currently this regression is blocking the migration of pyjwt to testing > [1]. Due to the nature of this issue, I filed this bug report against > both packages. Can you please investigate the situation and reassign the > bug to the right package?
As part of the "investigate" part - this might be related to a hotfix introduced in azure-cli 2.26.1 [1], which includes a change on how the "jwt.decode()" call related to the "verify" parameter [2]. pyjwt seems to have deprecated it in its 2.0 release [3] (and a number of similar in its upstream repo also point to that parameter). [1] https://github.com/MicrosoftDocs/azure-docs-cli/blob/master/docs-ref-conceptual/release-notes-azure-cli.md#storage-2 [2] https://github.com/Azure/azure-cli/pull/18811 [3] https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst#dropped-deprecated-verify_expiration-param-in-jwtdecode -- Diego M. Rodriguez
