I'm noting for posterity of this thread that I've opened a ticket and issued a
pull-request.
Ticket: https://code.djangoproject.com/ticket/24639
PR: https://github.com/django/django/pull/4497
--
You received this message because you are subscribed to the Google Groups
"Django developers
On 04/13/2015 12:13 PM, Aymeric Augustin wrote:
[snip]
> Do you think the backwards-incompatibilities are acceptable?
I think so, yes. It really isn't good behavior for Django to be
automatically installing such global adapters and converters.
Perhaps the release notes documenting this backwards-
Hello,
On databases that don't support time zones -- SQLite, MySQL, Oracle (*) -- the
implementation of time zone support I added in Django 1.4 defines:
1. A global converter, e.g. `parse_datetime_with_timezone_support` for SQLite,
which processes values returned by the database for datetime c
As long as it doesn't hurt we can keep em there -- remove as soon as they
cause a problem ;)
On Monday, April 13, 2015 at 4:30:01 PM UTC+2, Tim Graham wrote:
>
> I just discontinued the 1.3 docs on docs.djangoproject.com, they are
> still available on django.readthedocs.org. Do you think we shou
I just discontinued the 1.3 docs on docs.djangoproject.com, they are still
available on django.readthedocs.org. Do you think we should keep it there
or not?
On Thursday, August 7, 2014 at 7:45:15 AM UTC-4, Tim Graham wrote:
>
> I'm in favor of discontinuing older version of the docs. I recently
