Fellow Report - April 16, 2016
Triaged
---
https://code.djangoproject.com/ticket/26488 - migrate raises
InvalidBasesError if you rename a multitable inheritance base model
(accepted)
https://code.djangoproject.com/ticket/26491 - Duplicated queries with
nested prefetch (duplicate)
https://code.djangoproject.com/ticket/26494 - executable flags lost when
using an archive as a project/app template (accepted)
https://code.djangoproject.com/ticket/26487 - Use EHLO after
smtplib.SMTP_SSL too (accepted)
https://code.djangoproject.com/ticket/26493 - Document how built-in signals
are sent (fixed)
https://code.djangoproject.com/ticket/26501 - Docs for reusable apps is
missing {% extends "base.html" %} (duplicate)
https://code.djangoproject.com/ticket/26503 - SessionStore nonexistent key
example is outdated (accepted)
https://code.djangoproject.com/ticket/26504 - Prevent logging warnings for
page "Not Found" before redirect to language-prefixed page (accepted)
https://code.djangoproject.com/ticket/26502 - Lookup of attribute 'id' on
model inheritance models in InlineModelAdmin fails when using fk_name of
parent model (invalid)
https://code.djangoproject.com/ticket/26507 - Add autoreloading to the
cached template loader (duplicate)
Authored
https://github.com/django/django/pull/6444 - Refs #22936 -- Moved
IntegerField.get_prep_lookup() logic to lookups.
https://github.com/django/django/pull/6441 - Fixed #26486 -- Fixed a
select_related() + defer() MTI edge case.
https://github.com/django/django/pull/6452 - Refs #26502 -- Added choices
to Form.__getitem__() KeyError message.
https://github.com/django/django/pull/6454 - Removed various
unused/untested code in django.db.models.fields.
Reviewed/committed
--
https://github.com/django/django/pull/6437 - Split form's test_fields.py
into different files.
https://github.com/django/django/pull/6362 - Fixed #26432 -- Fixed size
tuple order when using numpy reshape on a GDALBand.
https://github.com/django/django/pull/6329 - Refs #16508 -- Renamed the
current "virtual" fields to "private".
https://github.com/django/django/pull/6467 - Fixed #26509 -- Deprecated the
contrib.gis.utils.precision_wkt() function.
https://github.com/django/django/pull/6427 - Fixed #26085 -- Fixed
contenttypes shortcut() view crash with a null fk to Site.
Reviews of core dev work
https://github.com/django/django/pull/6440 - Refs #17635 -- Tested the Cast
function in a geography to geometry context.
https://github.com/django/django/pull/6257 - Fixed #19567 -- Added
JavaScriptCatalog and JSONCatalog class-based views.
https://github.com/django/django/pull/6462 - Fixed #26510 -- Allowed
dim/trim/precision as WKTWriter init arguments
https://github.com/django/django/pull/6466 - Fixed #25951 -- Trimmed
default representation of GEOSGeometry
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/23a740a0-b289-41ca-bb52-d9f31e3b5730%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: collectstatic - override default ignore list
Claude proposed a PR which simply adds the setting as an AppConfig attribute: https://github.com/django/django/pull/6460 Feedback would be welcome as to whether this seems sufficient or if we need something more complex. I imagine this pattern will become fairly common if we decide to move in this direction. On Thursday, July 3, 2014 at 10:47:16 AM UTC-4, Andre Terra wrote: > > > On Thu, Jul 3, 2014 at 3:12 AM, Aymeric Augustin < > aymeric@polytechnique.org > wrote: > >> My concern -- and the reason why I started talking about an API -- is, >> if every app clutters the AppConfig namespace with arbitrary names, >> improvements to AppConfig may create name clashes. >> > > Hence my suggestion of encapsulating all those different "settings" in > AppConfig.settings. > > Cheers, > AT > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e36b821f-e9d7-44cd-aaa6-2d09597448f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: JsonpResponse subclass of HttpResponse helps easily create JSONP-encoded responses.
On Saturday, April 16, 2016 at 4:06:04 AM UTC+2, brigh...@gmail.com wrote: > > JsonpResponse isn't needed for most use cases. But is needed for some use > cases. > Like which? I think this should better live outside of Django. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/012f75ad-46d1-4519-9146-c53995fb8a1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Make template caching a feature of the Django template engine
Hi everybody, Tim pointed me to this discussion here and I support the overall goal. It accelerates development, especially when designing somewhat prettier Web pages. Quoting my quite naive approach from the issue tracker (https://code.djangoproject.com/ticket/26507#comment:2): """ I don't know if I would agree with the new title. Actually, I do not want to reload/replace the already loaded template. Looking at the source, I would say, we could make 'Loader.cache_key' respect the mtime of the first found template. So, they are two versions of the template in the cache but a cache does not need to be perfect after all and the increased memory footprint would not even matter in development. """ Do you think that's a feasible solution? Sven -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/81c26c94-bc52-4220-afb4-abedd06e27d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
