Upgrading django-cors-headers 1 to 2
Breaking1.3.1 → 2.5.3Breaking1New1Changed4Fixed6Other4
BreakingUpgrade verdict
1 breaking change.
In plain terms
- The built-in CorsModel database model is gone. If you used it, create your own model based on the new AbstractCorsModel and point it at the old table name to keep your data.
Must act 1 item needs code or config changes
Requires Python >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.* from 2.4.1 (none stated before).
Adds django >=1.11.
Installs 3 packages in all (was 0).
What you must change
Breaking1
Removes the undocumented CorsModel, which caused migration issues; users must define their own model inheriting AbstractCorsModel.
CorsModelAbstractCorsModeldb_table