Skip to content

Commit ad562c6

Browse files
committed
Copier Template: Add CPython 3.14 and PyPy 3.11 to answers file.
1 parent 9f76453 commit ad562c6

File tree

2 files changed

+13
-51
lines changed

2 files changed

+13
-51
lines changed

.auxiliary/notes/todo.md

Lines changed: 9 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
# TODO Items
22

3+
- Suppress PyPy 3.11 with Rust extension until Maturin supports it.
4+
- Suppress Python 3.13 and 3.14 with Rust extension until Maturin supports it.
5+
36
## Future Enhancements
47

58
### Documentation URL Support for docs-* Tags
@@ -17,68 +20,25 @@
1720

1821
**Priority:** Future enhancement - current `/stable/` approach is functional for immediate needs.
1922

20-
## Post-1.29 Development Ideas
21-
22-
### High Priority
23-
24-
#### Create tests/README.rst
25-
**Goal:** Document testing conventions and architecture for contributors.
26-
**Details:** Create comprehensive README consistent with write-tests command and documentation/common/tests.rst guidance. Include coverage expectations, test organization, and examples.
27-
**Why:** Complements our new write-tests command and improves developer experience.
28-
29-
#### Add Github Release Poller to Release Workflow
23+
### Add Github Release Poller to Release Workflow
3024
**Goal:** Improve release workflow reliability by ensuring Github release is registered before artifact publication.
3125
**Details:** Add polling step to wait for Github API to register new release before attempting to publish artifacts. Current workflow occasionally fails due to API delays.
3226
**Why:** Solves real production reliability issue we've experienced.
3327

34-
### Medium Priority
35-
36-
#### Improve Test Coverage
28+
### Improve Test Coverage
3729
**Goal:** Increase test coverage while avoiding integration test hazards.
3830
**Details:** Carefully add tests for uncovered code paths, being mindful of integration tests that might clobber production state. Focus on unit tests and safe integration scenarios.
3931
**Challenges:** Need to identify safe vs. risky integration test scenarios.
4032

41-
#### Add MCP Server Support to Claude GitHub Workflow
33+
### Add MCP Server Support to Claude GitHub Workflow
4234
**Goal:** Enhance automated code analysis and testing capabilities.
43-
**Details:** Add useful MCP servers (text-editor, ruff, pyright, context7) to the claude GitHub workflow to improve code quality and analysis automation.
35+
**Details:** Add useful MCP servers (text-editor, pyright, context7) to the claude GitHub workflow to improve code quality and analysis automation.
4436
**Why:** Could significantly improve automated testing and code analysis capabilities.
4537

46-
### Lower Priority
47-
48-
#### Enhance Write-Tests Command
49-
**Goal:** Improve write-tests command based on usage experience.
50-
**Details:** Add features like coverage gap analysis, test template generation, or integration with specific testing frameworks based on real usage patterns.
51-
52-
#### Add More Custom Slash Commands
53-
**Goal:** Expand Claude Code integration with project-specific workflows.
54-
**Ideas:**
55-
- `/analyze-coverage` - Deep dive into coverage gaps
56-
- `/update-template` - Streamlined copier template updates
57-
- `/validate-release` - Pre-release validation checklist
58-
59-
#### Claude Code Architectural Agents
60-
**Goal:** Create specialized Claude Code agents for architectural work and Python design.
61-
**Ideas:**
62-
- `architect` - For making architectural decisions, creating ADRs, reviewing system design
63-
- `python-designer` - For Python-specific design decisions, API design, module structure
64-
- `requirements-analyst` - For PRD creation, requirements gathering, user story development
65-
- Integration with the new architecture documentation framework
66-
67-
#### Project Structure Documentation
68-
**Goal:** Add template/documentation/architecture/structure.rst with starter outline.
69-
**Details:** Document the standard project structure pattern generated from our template to help new contributors understand the architectural conventions.
70-
**Why:** Provides immediate context for the consistent patterns across template-generated projects.
71-
72-
#### Documentation Improvements
73-
**Goal:** Enhance project documentation and developer experience.
74-
**Ideas:**
75-
- API documentation improvements
76-
- Tutorial content for template usage
77-
78-
#### Release Workflow Enhancements
38+
### Release Workflow Enhancements
7939
**Goal:** Further improve release automation and reliability.
8040
**Ideas:**
8141
- Automated release notes generation improvements
8242
- Multi-stage release validation
8343
- Rollback procedures documentation
84-
- Release metrics and monitoring
44+
- Release metrics and monitoring

copier.yaml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,26 +57,28 @@ python_versions:
5757
- '3.11'
5858
- '3.12'
5959
- '3.13'
60+
- '3.14'
6061
default:
6162
- '3.10'
6263
- '3.11'
6364
- '3.12'
6465
- '3.13'
66+
- '3.14'
6567
validator: >-
6668
{% if not python_versions %}
6769
Must specify at least one Python version
6870
{% endif %}
6971
7072
pypy_versions:
71-
# Note: 2025-03-24: PyPy 3.11 not supported in Hatch yet.
72-
# Still in beta from upstream.
7373
type: str
7474
help: Supported PyPy Python versions
7575
multiselect: true
7676
choices:
7777
- '3.10'
78+
- '3.11'
7879
default:
7980
- '3.10'
81+
- '3.11'
8082

8183
python_version_min:
8284
type: str

0 commit comments

Comments
 (0)