Python Guidelines

Make the design calls no linter can check — where an oversized file splits, whether a name or docstring carries meaning, whether an abstraction earns its keep, when a suppression is legitimate, and how to satisfy a size or complexity ratchet without gaming it. Use when a size or complexity gate has just failed, before adding a noqa or nosec, when deciding what to raise and what to catch, or when shared state is reached from more than one concurrent lane.

niksavis Updated 2 repo stars

File contents

niksavis/basicly commit b109b14900

Frequently asked questions

npx get-skill add niksavis/python-guidelines-2