On Wednesday, September 24, 2014 8:24:28 AM UTC+9:30, Shai Berger wrote:
>
> Hi all,
>
> I gave a talk to a local user-group about the migrations in 1.7, and some
> people in the audience raised things they would like to be able to do, and
> are
> not supported by the current framework; thoug
I have some comments regarding 3.
The idea, if I've understood your recount of the problem, is a good one.
You want to be able to run a backwards-compatible migration (database works
with app-state X and X+1), upgrade your application servers, and then run
another migration that works with app-
Hi all,
I gave a talk to a local user-group about the migrations in 1.7, and some
people in the audience raised things they would like to be able to do, and are
not supported by the current framework; thought it would be nice to bring them
here.
Two issues were about handling migrations at the
I don't think compilation At Package installation time is a good idea
because it would mean requiring GNU get text msgfmt binary availability at
that point.
I'd say the way to go is to perform that .mo files generation at release
time so that msgfmt needs to be installed on the Django team release
Hi. I have some questions about implementation.
It would be nice to compile those .mo files at package build time.
>
It's about setup.py? Or compilation must be in another place?
One more question - if it should be in setup.py, will I be able to run
compilemessages command during package install
