tickets: 17208
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 17208 | 2011-11-12 09:22:11 | 2016-10-20 22:41:22 | 2022-03-06 04:05:15.782355 | Accepted | assigned | contrib.admin | Cleanup/optimization | Normal | dev | Dogfood class-based views in contrib.admin | This is something that I believe was discussed at DjangoCon, as well as in the django-dev mailing list and on IRC. It would be good to do a) on principle, b) to make the admin views easier to extend, and c) to potentially find and correct issues in the generic class-based views. Naturally, any solution would need to be backwards-compatible. | yoongkang | melinath | class-based views admin | 0 | 1 | 0 | 0 | 1 | 0 |