+1 for this, I felt the same dilemma recently while working on some research work.
On Mon, Jul 4, 2022 at 7:58 PM Petr Viktorin <encukou@gmail.com> wrote:
Hello list, The _testcapimodule.c file is growing very big, to the point where I started to dread touching it. When adding a test I'm never sure if I'm missing a group of similar ones that it should be grouped with. It's difficult to get a sense of how tested some area of the API is. Code for a single topic is frequently split across several places (functions, type definitions, slot entries...), making me reach for my editor's bookmark feature more than I'd like. Do you feel the same?
I opened an issue, and a PR where I suggest how to split things up. Preferably, please keep the discussion there.
capi-sig mailing list -- capi-sig@python.org To unsubscribe send an email to capi-sig-leave@python.org https://mail.python.org/mailman3/lists/capi-sig.python.org/ Member address: nanjekyejoannah@gmail.com
-- Best, Joannah Nanjekye
*"You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program." Alan J. Perlis*