django.git/tests/postgres_tests/array_default_migrations/0001_initial.py, branch 1.8b1 django http://cgit.adnoto.dev/django.git/atom?h=1.8b1 2015-02-13T13:39:50Z [1.8.x] Refs #22962 -- Made test case use non-conflicting table names 2015-02-13T13:39:50Z Markus Holtermann info@markusholtermann.eu 2015-01-22T03:26:37Z urn:sha1:45d93baf518218c39b70fbc1eb35e9b53f66cf98 Backport of b06935a486e633e9732bce2bc5f796eb437b2531 from master [1.8.x] Sorted imports with isort; refs #23860. 2015-02-09T19:24:06Z Tim Graham timograham@gmail.com 2015-02-09T18:19:34Z urn:sha1:a8b70d251d238b4e6cfc7bb4296da15494f8dff3 Backport of 0ed7d155635da9f79d4dd67e4889087d3673c6da from master Fixed #22962 -- Default values for ArrayField with migrations. 2014-07-29T09:37:11Z Marc Tamlyn marc.tamlyn@gmail.com 2014-07-15T11:30:34Z urn:sha1:ef9f109013adc6e140c1a71d874aa88e893657b7 Fields normally try to force the default value to a string. As translatable strings are not valid default values for ArrayField, we can remove this behaviour which was causing issues with some migrations. Thanks to @schinckel for the report.