We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operating system: Debian GNU/Linux sid Python version: 3.8~b2 Black version: f3bb22a Does also happen on master: yup
Hello,
input code:
def test() -> None: assert mgf_sha2_256_meta == pss.parse_pss_options( pub, def_hash, rsa.PssOptions(mgf_alg=rsa.MgfAlgorithm(rsa.MgfAlgorithmId.MGF1))).mgf_alg
output code:
def test() -> None: assert ( mgf_sha2_256_meta == pss.parse_pss_options( pub, def_hash, rsa.PssOptions(mgf_alg=rsa.MgfAlgorithm(rsa.MgfAlgorithmId.MGF1)), ).mgf_alg )
The placement of the == operator looks very strange to me.
==
I'd prefer one of those:
or
def test() -> None: assert mgf_sha2_256_meta == pss.parse_pss_options( pub, def_hash, rsa.PssOptions(mgf_alg=rsa.MgfAlgorithm(rsa.MgfAlgorithmId.MGF1)), ).mgf_alg
If the actual result is by intention, is there any document that describes the rationale behind this decision?
Thanks!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Operating system: Debian GNU/Linux sid
Python version: 3.8~b2
Black version: f3bb22a
Does also happen on master: yup
Hello,
input code:
output code:
The placement of the
==
operator looks very strange to me.I'd prefer one of those:
or
If the actual result is by intention, is there any document that describes the rationale behind this decision?
Thanks!
The text was updated successfully, but these errors were encountered: