I'll simply say that while I am disappointed that there are so many
frictions here for whatever reason, I *strongly* appreciate the work done
to update threading, I get a deep sense of satisfaction using *correct*
naming conventions whenever using this library, and am glad that it got
through
IMO (a subset of) pytest is the superior unit-testing framework. Just
having functions prefixed with `test_` is easy and intuitive. It also works
well with xdoctest, but I would use it even if that wasn't the case. (That
being said, I think the current implementation of fixtures - where you
can't
Christopher Barker writes:
+1 to your earlier comment along the lines of "Java flavor is an issue
(sometimes) worth fixing, non-PEP8 identifiers is not." (I do not
claim Chris signs on to my formulation, I'm riffing on his. ;-)
> Note that a LOT of major projects dumped unittest years ago—
On Fri, 12 Nov 2021 at 03:46, Steven D'Aprano wrote:
>
> On Thu, Nov 11, 2021 at 10:06:45PM -0500, Ricky Teachey wrote:
>
> > Is there a standard idiom-- perhaps using a type-hint-- to signal to the
> > IDE/linter that my user-defined class is intended to be used as a
> > function/factory, and
