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 issu
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 tem
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.djangopr
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
