On Mon, 2019-12-02 at 10:23 +1100, Andrew Donnellan wrote:
> On 8/11/19 1:01 am, Daniel Axtens wrote:
> > Stephen Finucane writes:
> >
> > > Two issues here. Firstly, the use of the 'USE_I18N'. The Django docs
> > > describe this as such:
> > >
> > >A boolean that specifies whether Django’s
On 8/11/19 1:01 am, Daniel Axtens wrote:
Stephen Finucane writes:
Two issues here. Firstly, the use of the 'USE_I18N'. The Django docs
describe this as such:
A boolean that specifies whether Django’s translation system should
be enabled. This provides an easy way to turn it off, for per
On Wed, 2019-11-06 at 14:53 +0800, Stephen Finucane wrote:
> Two issues here. Firstly, the use of the 'USE_I18N'. The Django docs
> describe this as such:
>
> A boolean that specifies whether Django’s translation system should
> be enabled. This provides an easy way to turn it off, for perform
Stephen Finucane writes:
> Two issues here. Firstly, the use of the 'USE_I18N'. The Django docs
> describe this as such:
>
> A boolean that specifies whether Django’s translation system should
> be enabled. This provides an easy way to turn it off, for performance.
> If this is set to False
Two issues here. Firstly, the use of the 'USE_I18N'. The Django docs
describe this as such:
A boolean that specifies whether Django’s translation system should
be enabled. This provides an easy way to turn it off, for performance.
If this is set to False, Django will make some optimizations
