#8860 closed (invalid)
Where should form classes and formset classes be defined?
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | forms | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The current documentation doesn't say where form classes and formset classes and so on should be defined. Should they be defined in module models.py or in a separate module forms.py or somewhere else altogether? I think the situation is analogous to admin information which eventually was moved from models.py to admin.py.
Change History (3)
comment:1 by , 16 years ago
| Version: | 1.0 → SVN |
|---|
comment:2 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
There's no requirement that they be defined in any specific place; you're free to define your form-related stuff anywhere you like. For further questions, please consult the archives of the django-users list, where questions about best practices for application layout have been discussed multiple times.