Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .bumpversion.toml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
# https://peps.python.org/pep-0440/

[tool.bumpversion]
current_version = "0.3.2.dev2"
current_version = "0.3.2.dev8"
parse = """(?x)
(?P<major>0|[1-9]\\d*)\\.
(?P<minor>0|[1-9]\\d*)\\.
Expand Down
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -180,5 +180,7 @@ cython_debug/
.vscode/
requirements.txt
certs/
.idea/
.DS_Store

CLAUDE.md
32 changes: 32 additions & 0 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,38 @@ Every code change must be evaluated against these principles:

Before writing any code, ask: "Is this the most minimal way to achieve this? Can I remove anything?"

### Prohibited Patterns
The following patterns are **strictly prohibited** in this codebase:

1. **No `hasattr()`, `getattr()`, `setattr()`**: These indicate poor type design. Use explicit type checks (`is None`, `is not None`) or proper type annotations instead. If an attribute might not exist, the class design is wrong.
2. **No `from __future__ import annotations`**: Use direct imports and string literals for forward references when needed.

### Docstring Standard (Google Style)
All docstrings must follow Google style with these sections (when applicable):

```python
def method(self, param1: str, param2: int) -> bool:
"""Brief one-line description.

Longer description if needed (optional).

Args:
param1: Description of param1.
param2: Description of param2.

Returns:
Description of return value.

Raises:
ValueError: When validation fails.

Yields:
Description of yielded values (for generators).
"""
```

Keep docstrings lean and professional. No flowery language, no numbered steps, no obvious explanations.

### Code Organization
- **Encapsulation**: Keep related functionality together within classes
- **Private methods**: Only create private methods (`_method_name`) if the code is reused within the class
Expand Down
Loading
Loading