Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/python-patternsAPIs, SaaS e identidade

python-patterns

⁨Pythonic patterns for readable, robust Python: typing, error handling, data modeling, iteration, resource management, threading/process/subinterpreter primitives, project layout, and tooling. Use when writing or reviewing Python code and APIs. For measurement/GIL/JIT use python-performance; for asyn⁩

v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/python-patterns

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
29FCX+9SmF…AMF5flDw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotecf84dbdd…d893c911
cf84dbddde45…f266d893c9119 arquivos · ⁦8.9 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/python-patterns@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

This skill is for day-to-day Python code quality: readability, correctness, maintainability.

If you are doing asyncio-heavy work, prefer python-async-patterns. If the task is profiling, GIL/free-threading, or experimental JIT, use python-performance.

When to activate

  • Writing/refactoring Python modules, libraries, services
  • Reviewing PRs for idioms, clarity, and footguns
  • Introducing typing or improving error handling
  • Designing lightweight data models and APIs
  • Choosing threads vs processes vs subinterpreters (not asyncio)

Core principles (high signal)

  • Readability beats cleverness.
  • Be explicit at boundaries (I/O, parsing, network). Keep inner code simple.
  • Prefer small, typed functions with clear names.
  • Use context managers for resource safety.
  • Raise specific exceptions and preserve causes (raise ... from e).

Outcome expectations

  • Code is readable; intent is clear from names and structure, not comments.
  • All public APIs have type annotations; error boundaries are explicit.
  • Resource cleanup is deterministic (via context managers, no __del__).
  • Exceptions are domain-specific and chain causes; no silent failures.

  1. Design module interfaces with clear input/output types and error contracts.
  2. Use context managers for all resource acquisition.
  3. Validate at I/O boundaries; raise specific errors with cause chaining.
  4. Apply ruff, mypy (on public APIs), and pytest baseline in CI.
  5. Review code for footguns (mutable defaults, bare except, type hiding).

Quick review checklist

  • No mutable default arguments; None sentinel used
  • is None / is not None (not == None)
  • Specific except clauses; no bare except:
  • Types: public functions/classes have annotations; 3.12+ type-parameter syntax; T | None not Optional[T]
  • Files/paths use pathlib.Path (Path.walk 3.12+); not os.path string soup
  • Iteration uses comprehensions/generators only when simple
  • CPU-bound fan-out uses executors from concurrency.md, not unbounded Thread spawns

Resources

Load on demand:

  • references/typing.md — load for annotations, PEP 695 generics, Protocols, 3.14 deferred evaluation
  • references/errors.md — load for exception hygiene, ExceptionGroup / except*, finally control flow
  • references/data-models.md — load for dataclasses, copy.replace, StrEnum, t-strings (3.14)
  • references/iteration.md — load for comprehensions, generators, itertools.batched, match
  • references/resources.md — load for context managers and pathlib
  • references/concurrency.md — load for threads, concurrent.futures, queues, multiprocessing start methods, InterpreterPoolExecutor
  • references/layout-tooling.md — load for pyproject.toml, ruff/mypy/pytest, removed stdlib modules
  • references/performance.md — one-screen "don't micro-optimize here"; real measurement is python-performance

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd568cf84dbddAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login