Done. Will debug the [French] out of this tomorrow at the sprint.
Le 3 juin 2015 16:01, "Tim Graham" a écrit :
> Yes, it looks like a legitimate bug. Please file a Trac ticket.
>
> On Wednesday, June 3, 2015 at 8:55:47 AM UTC-4, is_null wrote:
>>
>> Hi all,
>>
>> I've had this issue reported for
Maintaining some ability for test applications to have no migrations is
very important for Django's own test suite and also other tools such as
djangobench. If we're going to maintain some form of code path for that, we
should expose it publicly as well.
Marc
On 3 June 2015 at 14:29, Markus Holte
Yes, it looks like a legitimate bug. Please file a Trac ticket.
On Wednesday, June 3, 2015 at 8:55:47 AM UTC-4, is_null wrote:
>
> Hi all,
>
> I've had this issue reported for the second time in
> django-autocomplete-light's tracker.
>
> For the first time on Jan 16th 2014 by a user whom I thou
Thanks Tim for your response and sharing the report of the survey.
As mentioned in the introduction, we will (give our best to) keep aligned
to the official releases and do not intend to bypass the security concept
of Django.
We will update the project README to communicate the concept
correctl
When do you drop support for old versions of Django? The main concern I
have is that it somewhat encourages running on unsupported and insecure
versions of Django (currently 1.5, 1.6; and 1.4 will be end of life in
October). Therefore I don't thinking giving it an official blessing is a
good id
After some discussion with other members of the core team, we think that we
might re-evaluate the point of dropping support for apps without
migrations. But this highly depends on the outcome of what Andrew is going
to achieve in https://code.djangoproject.com/ticket/24481#comment:6 with
regard
Hi all,
I've had this issue reported for the second time in
django-autocomplete-light's tracker.
For the first time on Jan 16th 2014 by a user whom I thought was a
django core-dev so I didn't really bother following up on this - I beg
your pardon for that.
This has also be reported a few hours a
2015-06-02 18:27 GMT+01:00 Emil Stenström :
> That's a problem that I hadn't thought about. I was hoping that querysets
> where always serializable, but I didn't think of datetime and decimal (and
> others), which people might send to their views. Are there other pitfalls
> here? Maybe this could
After discussion with Markus Holtermann, we decided that we need to
deprecate internal syncdb in 1.9
(https://github.com/django/django/blob/7c637a3aaec311269bf863c220bf894eebbe7c7c/django/core/management/commands/migrate.py#L136)
The fact that apps without migrations are not supported, which is
TLDR; Introducing django-compat - arteria's solution for for- and
backwards compatibility from Django 1.4.x to 1.8.x./1.9.x
SITUATION
We really love how Django evolves and how the core gets better and better.
New major versions of the framework that comes with changes, bugfixes and
new feat
10 matches
Mail list logo
