Opened 11 years ago
Last modified 11 years ago
#23892 closed Cleanup/optimization
Make deconstructible classes forwards compatible — at Initial Version
| Reported by: | Markus Holtermann | Owned by: | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.7 |
| Severity: | Normal | Keywords: | 1.8 |
| Cc: | info+coding@… | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The migration operations don't accept any additional arguments (neither *args nor **kwargs). This will lead to problems in older (>=1.7) Django versions if the the migration files for 3rd party apps have been created with newer Django versions in case the new operations have a different constructor signature. Thus **kwargs should be added to all operation signatures.
See the discussion on django-developers for details: https://groups.google.com/forum/#!topic/django-developers/nWHVaG6gK0Y
Note:
See TracTickets
for help on using tickets.