> Is that always available these days? (I'd guess yes.)
I too would guess yes. I believe any reasonably modern text editor will
support
UTF-8 and even likely default to saving in that encoding. I know mine does.
> Is is something we want to impose? Not sure. Are there people doing
> otherwise?
For some reason the text is white… Here it is in black:
Hey Marcin,
The problem is that data migration based on app layer (python objects, ie.
Models and Managers here) will cause troubles after some time (when app is
changing).
In the other words - you cannot rely on your app layer when doing
Hey Marcin,
The problem is that data migration based on app layer (python objects, ie.
Models and Managers here) will cause troubles after some time (when app is
changing).
In the other words - you cannot rely on your app layer when doing database
changes. You should never do that, especially for
Well this is what we call as the downtime.
On Tuesday, 2 October 2018 06:17:10 UTC+5:30, martin_x wrote:
>
> Hi there,
>
> Thanks for making Django a great framework for starters :D
>
> Recently my team have run into problems when trying to remove a database
> column from the model without
You could include the a python file where you can place all the strings
which you manually wanted to add and then use the *makemessages *management
command. I think it will serve the purpose.
I think this behaviour of commenting out manually added strings by
*makemessages *management command
Hello,
> Do you know what OS/browser combination you were referring to with "Windows
> (which, I'm afraid, has its own time zone name)"?
At the system level, I'm not sure Windows is using (or was using) the timezone
database (formerly known as the Olson database). I remember this being an