Hello Andres,
We both seem to agree with the status quo — supporting both text and bytes.
On 24 Dec 2016, at 00:36, 'Andres Mejia' via Django developers (Contributions
to Django itself) wrote:
> On 12/22/2016 05:15 PM, Aymeric Augustin wrote:
>> export SECRET_KEY=… # generated with pwgen -s 50
Triaged
---
https://code.djangoproject.com/ticket/25754 - Queryset repr is not
displayed on IPython >= 3.0 REPL if a NotImplementedError is raised
(invalid)
https://code.djangoproject.com/ticket/27619 - Queries where column name
includes a '%' character break when using MySQL (duplicate
There is a history of problems related to the coupling between forms and
models. For example, when a user suggested to pass a field instance to the
model field to make it default [0], or when I suggested to improve
formfield [1]: it was rejected because it would increase the coupling
between forms
Hi, it seems like you keep starting new threads about the same topic
without mentioning the previous threads and summarizing those discussions.
For example, you should layout the problem in more detail and explain what
"pretty much everybody would like to see a fix appear" means. I'm not sure
w
Hi all,
Currently, the model fields define which form fields should be used for
them by default. That's why we have to specify form stuff such as "blank"
when declaring our model fields, and pretty much everybody would like to
see a fix appear.
Would it be possible to add a new option for users t
