On 18 août 2015, at 01:28, Tim Graham wrote:
> Unless someone can present an argument for keeping IE8 support, I wouldn't
> worry about it considering it will be end of life about 1 month after the
> release of Django 1.9.
Let’s just make sure the admin stays usable, even if it looks bad. Sinc
I also had the idea of upgrading jQuery to jQuery 2 which drops support for
IE6/7/8, but I guess this will break all the JavaScript in the admin under
those browsers. Do you think that's unacceptable at this time? If so, could
you propose an alternate timetable for the upgrade?
On Tuesday, Augu
I don't know about schedule, but caniuse reports IE8 browser usage at 1.5%,
more than IE9 or IE10.
There's an argument we shouldn't be "enabling" people still using XP who
are stuck on IE8, and this is a decreasing problem, but I don't think we
can tie ourselves to Microsoft's support dates.
On 1
Hey,
Looking at some browser market share stats
(http://www.sitepoint.com/browser-trends-august-2015-chrome-exceeds-50/
, disclaimer:
http://www.sitepoint.com/how-browser-market-share-is-calculated/) IE8
seems hardly be used anyway. Furthermore, with the dropped support for
IE8 (and 9+) on Jan 12
Hi all,
Thanks for detailed response. I thought over the described expressions/
transforms patches and here are my thoughts about the best way to
implement simplified lookups.
Firstly, I want to describe which properties of the new syntax seem to be
important:
1. Using Python operators to do bas
I see. Could this concern be addressed by adding it to the checks
framework, so that it throws a warning if there are ever two commands with
the same name?
On Mon, Aug 17, 2015 at 11:16 AM Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> 2015-08-17 16:54 GMT+02:00 Mike Lissner :
>
This is a deliberate approach you would use - South used it for years to
customise syncdb.
call_command is intended as a python API for testing `$ django-admin foo`.
Two of your arguments are based around IDE usage, which I don't think is a
valid argument, and the third is about reducing string ma
Just a quick thought: I could imagine some newbies could get confused by
the python-like syntax and try to do:
Equal(P.user.get_full_name(), 'Bob Someone')
I don't think it's not a huge deal, but worth noting.
On Tuesday, August 18, 2015 at 8:00:17 AM UTC-4, Alexey Zankevich wrote:
>
> Hi all,
Hi Marc, Mike, Aymeric,
On 08/18/2015 06:52 AM, Marc Tamlyn wrote:
> This is a deliberate approach you would use - South used it for years to
> customise syncdb.
>
> call_command is intended as a python API for testing `$ django-admin
> foo`. Two of your arguments are based around IDE usage, whic
On Tuesday, August 18, 2015 at 12:00:30 PM UTC-4, Carl Meyer wrote:
>
> (Doc patches to better reflect that principle in the management command
> docs are welcome, IMO.)
>
> Yeah, it's sounding like this is the change that's needed here. Probably
the place to do that is here:
https://docs.djan
On 08/18/2015 10:10 AM, Mike Lissner wrote:
> On Tuesday, August 18, 2015 at 12:00:30 PM UTC-4, Carl Meyer wrote:
>
>
> (Doc patches to better reflect that principle in the management command
> docs are welcome, IMO.)
>
> Yeah, it's sounding like this is the change that's needed here. Pr
I'm still thinking we shouldn't integrate any new query syntax into
1.9. Instead lets make it easy to create 3rd party apps that offer
different querying syntax, and then lets see which solution (if any)
gets popular enough to be integrated into Django.
- Anssi
On Tue, Aug 18, 2015 at 5:54 PM,
I strongly agree with the third party approach.
On 18 Aug 2015 17:49, "Anssi Kääriäinen" wrote:
> I'm still thinking we shouldn't integrate any new query syntax into
> 1.9. Instead lets make it easy to create 3rd party apps that offer
> different querying syntax, and then lets see which solution
+1 for making it doable for 3rd party apps.
Regards,
Michael Manfre
On Tue, Aug 18, 2015 at 12:49 PM, Anssi Kääriäinen
wrote:
> I'm still thinking we shouldn't integrate any new query syntax into
> 1.9. Instead lets make it easy to create 3rd party apps that offer
> different querying syntax, a
Today the Django team issued multiple releases -- Django 1.4.22, 1.7.10,
and 1.8.4 -- as part of our security process. These releases address a
security issue, and we encourage all users to upgrade as soon as possible.
More details can be found on our blog:
https://www.djangoproject.com/weblog/
Once Josh completes this patch https://github.com/django/django/pull/5090
(.filter method accepting class-based lookups and transforms), it will be
almost everything required by third-party apps. Is it going to be a part of
Django 1.9, by the way?
Additionally, for pure flexibility, next method an
I'd like to ask for a high-level API review of some proposed streaming API
additions (I have already given the patch a couple of detailed reviews, but
other eyes would be welcome on the details as well).
Summary:
* django.views.generic.base.StreamingTemplateView to stream a template
rather tha
On Tuesday 18 August 2015 14:29:15 Marc Tamlyn wrote:
> I don't know about schedule, but caniuse reports IE8 browser usage at 1.5%,
> more than IE9 or IE10.
>
> There's an argument we shouldn't be "enabling" people still using XP who
> are stuck on IE8, and this is a decreasing problem, but I don'
Hi Carl,
I know it's been a while since we discussed this, but today's security
release is the first one that's really affecting our product and we've
finally got things in shape to be able to start distributing unofficial
Django security releases (we've also just been swamped since our discuss
Hi all,
I'm volunteering myself to maintain both Oracle and Oracle GIS backends.
I've been developing applications based on Oracle for almost 20 years now and
I've been maintaining Oracle installations and databases.
I've been developing with Django and it's GIS parts with almost 10 years now.
I'll also stick my hand up to be involved with the Oracle backend, but not
the Oracle GIS backend. I don't have a lot of time available at the moment,
but I'll be able to support Jani and anyone else that's interested in
maintaining the backend.
Cheers
On Wednesday, 19 August 2015 16:36:23 UTC
21 matches
Mail list logo
