Changes between Version 1 and Version 2 of Ticket #15404, comment 1


Ignore:
Timestamp:
02/23/11 13:15:27 (9 years ago)
Author:
Łukasz Rekucki
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15404, comment 1

    v1 v2  
    1 Not all of those errors are related to unicode - most of them should disappear on lastest 1.2.X version. I runned Django's full test suite with {{{SECRET_KEY}}} being unicode and {{{DATABASES}}} containing unicode keys and only errors I get are related to {{{SECRET_KEY}}}. IMHO, there is nothing to fix here, because {{{SECRET_KEY}}} ''should be'' a byte-string - after all it's a series of random bytes.
     1Not all of those errors are related to unicode - most of them should disappear on lastest 1.2.X version. I runned Django's full test suite with {{{SECRET_KEY}}} being unicode and {{{DATABASES}}} containing unicode keys and only errors I get are related to {{{SECRET_KEY}}}. IMHO, there is nothing to fix here, because {{{SECRET_KEY}}} ''should be'' a byte-string - after all it's a series of random bytes. (Well, ok - maybe a docfix and a sanity check on startup).
    22
    33Could you provide an easy way to reproduce an error related to DATABASES setting ?
Back to Top