status of 1.10 release blockers
Time to kickoff the progress tracker for the next major release! At this time, I'm considering master feature frozen besides the tickets marked "ready for checkin" [1] and those tagged "1.10" [2]. Let me know if I missed anything critical. I'll continue working with the ticket owners to polish those patches. I'll also continue merging bug fixes until we create the stable/1.10 branch and issue the alpha release, which I'd like to do sometime next week. [1] https://code.djangoproject.com/query?status=assigned=new=Ready+for+checkin=id=summary=status=owner=type=version=priority [2] https://code.djangoproject.com/query?status=assigned=new=~1.10=Accepted=id=summary=status=owner=type=version=changetime=1=changetime -- 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/36f569dd-2fe3-4caf-ae3d-e04b71e3d87d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Fellow Report - May 14, 2016
Triaged --- https://code.djangoproject.com/ticket/26611 - Make "Share this traceback on a public Web site" feature on debug page optional (duplicate) https://code.djangoproject.com/ticket/26606 - 'string_if_invalid' option does not work with custom filter (invalid) https://code.djangoproject.com/ticket/18599 - GenericForeignKey field can't be set on init of model (fixed) https://code.djangoproject.com/ticket/26614 - Use constant_time_compare() in checking session auth hash in login() (fixed) https://code.djangoproject.com/ticket/26612 - SelectFilter2 Buttons Change URL (fixed) https://code.djangoproject.com/ticket/26607 - Add InlineModelAdmin.get_formset_initial_data(). (accepted) https://code.djangoproject.com/ticket/26605 - Abstract model inheriting concrete model crashes migrations (accepted) https://code.djangoproject.com/ticket/26604 - Add example of simple multiple file upload in documentation (accepted) https://code.djangoproject.com/ticket/18100 - Deleting model instances with deferred fields don't trigger deletion signals (fixed) https://code.djangoproject.com/ticket/26600 - map says a queryset is not iterable (needsinfo) Authored https://github.com/django/django/pull/6576 - Fixed #24046 -- Deprecated the "escape" half of utils.safestring. https://github.com/django/django/pull/6585 - Refs #24227 -- Removed ManyToManyField special casing in model_to_dict(). https://github.com/django/django/pull/6175 - Refactored managers inheritance (wrote documentation) Reviewed/committed -- https://github.com/django/django/pull/6300 - Fixed #25005 -- Made date and time fields with auto_now/auto_now_add use effective default. https://github.com/django/django/pull/6447 - Fixed #21231 -- Enforced a max size for GET/POST values read into memory. https://github.com/django/django/pull/6485 - Fixed #26429 -- Added a timestamp to merge migration names. https://github.com/django/django/pull/6451 - Fixed #26277 -- Added support for null values in ChoicesFieldListFilter. https://github.com/django/django/pull/6587 - Fixed #26333 -- Made GEOS Geometry classes deconstructible. https://github.com/django/django/pull/4815 - Fixed #24938 -- Added PostgreSQL trigram support. Reviews of core dev work https://github.com/django/django/pull/6586 - Fixed #24100, #24075 -- Made the migration signals dispatch its plan and apps and use them. https://github.com/django/django/pull/6243 - Fixed #25774 -- Added Extract and Trunc datetime functions. -- 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/f47d6d32-6155-419b-ab37-8a8bd380b354%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Template-based widget rendering
While testing this, I ran into a shortcoming with the fallback strategy for
backwards-compatibility.
If you have a DjangoTemplates backend configured with 'APP_DIRS': True (as
in the tutorial) and you try to visit /admin/auth/user/#/change/ which
renders the ReadOnlyPasswordHashWidget, the template system will crash with
TemplateDoesNotExist because it can find the widget's template using the
app_directories loader but not the 'django/forms/widgets/attrs.html'
template that the first template includes. Since the first template is
found using what's configured in TEMPLATES (which doesn't know about any of
the built-in form templates), the standalone engine needed to find the
built-in templates is ignored.
I guess it will affect every project that uses the admin. I can't think of
a simple solution other than adding a system check upgrade warning to
detect this situation ('django.contrib.admin' in INSTALLED_APPS but not
'django.forms') and advise the user to add 'django.forms' to
INSTALLED_APPS. Thoughts?
On Thursday, May 12, 2016 at 1:17:23 PM UTC-4, Carl Meyer wrote:
>
> On 05/12/2016 09:39 AM, Tim Graham wrote:
> > So this discussion doesn't stall the rest of the patch, I suggest
> > keeping the fallbacks for now and deprecation them later if they cause
> > confusion or other problems.
>
> Yes, I think that makes sense.
>
> Carl
>
>
--
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/2fa7c726-3549-4a02-a820-0aae79802a2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Unicode normalization for username field
Le jeudi 12 mai 2016 18:45:15 UTC+2, Tim Graham a écrit : > > Just to be sure, do you mean django.db.migrations (referencing the > appropriate validator in the migration file, I guess?) or some problem a > project would face when migrating from Python 2 to 3? > Both things, hopefully not an issue, but who knows? I have attached the new PR to the ticket. Claude -- 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/61b6ebe2-c2d3-4a82-96fb-0410a7502d5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
