This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, lys.nikolaou, pablogsal, slebedev
Date 2021-12-23.20:35:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1640291719.36.0.619323229429.issue46167@roundup.psfhosted.org>
In-reply-to
Content
It's not about an advantage, it's about removing the problem of what edit to make when working on


assert thing_that_has_a_meaningful_name.methods_have_good_names(value_from_somewhere) == other_thing_that_is_meaningful, "Description of what the issue is if this fails for humans, as if the names weren't enough"

and making that fit within whatever line length limit your codebase has.

put () in the wrong place and it triggers the long standing Python wart or parsing as a tuple.

rather than warn about the syntax wart, we should just do the thing code authors want in the first place.
History
Date User Action Args
2021-12-23 20:35:19gregory.p.smithsetrecipients: + gregory.p.smith, lys.nikolaou, pablogsal, slebedev
2021-12-23 20:35:19gregory.p.smithsetmessageid: <1640291719.36.0.619323229429.issue46167@roundup.psfhosted.org>
2021-12-23 20:35:19gregory.p.smithlinkissue46167 messages
2021-12-23 20:35:19gregory.p.smithcreate