Files
SpecterOps-Nemesis/projects
Lee Chagolla-Christensen e598535d4e more psycopg to asyncpg pools in file enrichment
- Replace psycopg_pool.ConnectionPool with asyncpg.Pool throughout file_enrichment service
- Store asyncpg pool in FastAPI app.state instead of global variable
- Update type hints
- Fix enrichment success tracking query typo in noseyparker
- Improve formatting in dotnet finding summaries (use code formatting for method names)
2025-10-25 17:54:19 -07:00
..
2025-08-29 15:24:32 -07:00
2025-10-25 16:18:24 -07:00
2025-08-29 15:24:32 -07:00
2025-08-29 15:24:32 -07:00
2025-10-25 10:41:20 -07:00
2025-06-13 11:33:07 +02:00

Naming Conventions

Projects and libraries should follow Python's PEP8 naming conventions:

Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged.

When an extension module written in C or C++ has an accompanying Python module that provides a higher level (e.g. more object oriented) interface, the C/C++ module has a leading underscore (e.g. _socket).