Fellow Report - January 9, 2015

[Tim Graham]

This is my second to last report before the fellowship pilot ends. If you’d 
like to see the program happen again, please encourage your company or 
organization to donate to the DSF 

.

Highlights of this week included reviewing many of the remaining large 
features for 1.8: Daniel’s _meta refactor work, Aymeric’s multiple template 
engines docs, Marc’s work on Range fields for contrib.postgres, and a large 
ORM patch from Anssi to leverage the new expressions functionality 
internally. I am pleased that we've finished all the major features we 
targeted during the 1.8 release planning [1] and that we're on schedule for 
an alpha release next week. Thank-you to everyone from the community for 
making it happen.


[1] https://code.djangoproject.com/wiki/Version1.8Roadmap

Report for week ending January 9, 2015:

Triaged

---

https://code.djangoproject.com/ticket/24089 - Misleading error raised 
during system check related to ModelAdmin (accepted)

https://code.djangoproject.com/ticket/24102 - SchemaEditor.create_model 
doesn't create a constraint name for unique_together (accepted)

https://code.djangoproject.com/ticket/24105 - When upload_to is callable, 
storage.get_valid_name() does not get called (accepted)

https://code.djangoproject.com/ticket/24081 - Latest six update broke 
Python 2.5 compatibility (fixed)

https://bitbucket.org/gutworth/six/issue/112/sixmovesreload_module-uses-deprecated-imp
 
- six.moves.reload_module uses deprecated imp module on Python 3.4+ 
(created; it causes a warning in Django’s test suite)

Authored



https://github.com/django/django/pull/3837 - [1.7.x] Increased the default 
PBKDF2 iterations.

https://github.com/django/django/pull/3839 - Updated release instructions 
with latest process.

https://github.com/django/django/pull/3855 - Fixed #24095 -- Prevented 
WarningLoggerTests from leaking a warnings filter.

https://github.com/django/django/pull/3860 - Fixed #24101 -- Fixed flaky 
admin_views selenium tests; refs #7361.

https://github.com/django/django/pull/3863 - Isolated some cache tests; 
refs #23947.

https://github.com/django/django/pull/3870 - Added best practices for 
versionadded/changed annotations.

Reviewed/committed

--

https://github.com/django/django/pull/3836 - Fixed #24072 -- Added support 
for wsgi.file_wrapper

https://github.com/django/django/pull/3846 - Fixed #24022 -- Deprecated the 
ssi tag.

https://github.com/django/django/pull/3114- Fixed #12663 -- Formalized the 
Model._meta API for retrieving fields.

https://github.com/django/django/pull/3840 - Fixed #24078 -- Removed empty 
strings from GenericIPAddressField

https://github.com/django/django/pull/3669 - Fixed #24020 -- Refactored SQL 
compiler to use expressions & refactored select_related() implementation

https://github.com/django/django/pull/3859 - Fixed #24098 -- Added no-op 
attributes to RunPython and RunSQL

Reviews of core dev work



https://github.com/django/django/pull/3838 - Fixed #24073 -- Deactivated 
translations when leave_locale_alone is False

https://github.com/django/django/pull/3828 - Fixed #8280 -- Allowed 
management command discovery for eggs

https://github.com/django/django/pull/3858 - Fixed #24099 -- Removed 
contenttype.name deprecated field

https://github.com/django/django/pull/3849 - Fixed #22583 -- Allowed 
RunPython and RunSQL to provide hints to the db router.

https://github.com/django/django/pull/3845 - Multiple template engines docs

https://github.com/django/django/pull/3478 - Fixed #24011-- Added Range 
fields for contrib.postgres
https://github.com/django/django/pull/3542 - Fixed #13165 -- Added edit and 
delete links for admin related fields.

-- 
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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1a9aef69-76c9-4791-ba7c-1eaba4f6fa93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.8 release blockers

[Tim Graham]

Here is the fifth update with several days to go until alpha. I believe we 
are on track for a feature freeze at the end of day on Monday. Let's see 
how things go, but I'd like to cut the stable/1.8.x branch and issue the 
alpha release by the following Friday (a week from today).

New blockers:

#24075  - Can't migrate 
contenttypes and auth to zero 
Owner: Simon
Status: This is an existing issue on 1.7, but addressing it seems to 
require (or at least, would be a lot easier) with the proposed new feature 
of adding a "plan" argument to the post_migrate() signal. There is a patch 
in the works.

Resolved since last time:

#23861 - 
 Fields referenced in 
migrations cannot be (re)moved, even if migrations have been squashed 

Owner: Tim
Now: I polished and committed the patch for this.
Last time: I committed a patch for the second ticket and will polish the 
patch for the first issue.

Most of the issues tagged "1.8-alpha" have been completed or deferred. The 
two main ones that remain are "Case/When expressions" and "Allowing 
expressions to be used in order_by queryset method." Depending on what 
progress is made over the weekend on these issues, they may or may not make 
it into 1.8.
https://code.djangoproject.com/query?status=assigned=new=~1.8-alpha

On Saturday, January 3, 2015 at 1:19:25 PM UTC-5, jdunck wrote:
>
> Thank you, Tim, for shepherding this.
> On Jan 3, 2015 8:09 AM, "Tim Graham"  
> wrote:
>
>> Here is the fourth update with a week to go until alpha. At this time, I 
>> am thinking we'll have the feature freeze on Monday, January 12 as planned, 
>> but perhaps issue the actual alpha release a couple days later just to give 
>> some time for some extra polish in case any large patches are committed 
>> next weekend.
>>
>> #23861 - 
>>  Fields referenced in 
>> migrations cannot be (re)moved, even if migrations have been squashed 
>> 
>> #23891  - Revise 
>> deprecation / removal timeline for IPAddressField 
>>  (resolved)
>> Owner: Tim
>> Now: I committed a patch for the second ticket and will polish the patch 
>> for the first issue.
>> Last time: I've implemented the system check solution I proposed and am 
>> waiting for review and/or concerns with this approach.
>>
>> After completing the issue above, I'll prioritize any issues here:
>>
>> https://code.djangoproject.com/query?status=assigned=new=~1.8-alpha
>>
>> Resolved since last time:
>>
>> #22340 -  
>>  Legacy Table Creation 
>> Methods Not Properly Deprecated 
>> 
>> Owner: Tim
>> Now: Resolved this by removing the deprecation as discussed in the ticket.
>> Last time: I took a closer look at this and don't think we need to do 
>> this deprecation at all as it doesn't seem to offer any benefits. See the 
>> ticket for details.
>>
>> #23745 - Migrations migrate is slow 
>> 
>> Owner: Claude/Markus
>> Now: Patch committed; thanks to Markus and Claude.
>> Last time: I committed the test that Markus wrote and Claude incorporated 
>> a fix from Markus so the branch appears about ready for merge. Markus will 
>> give it another review.
>>
>> -- 
>> 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-develop...@googlegroups.com .
>> To post to this group, send email to django-d...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/b196f095-530c-45ec-9b21-82fcd1c06ed8%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5680073d-8a2e-4370-945a-c18d846e1e25%40googlegroups.com.
For more options, visit 

documenting changes to the database backend API

[Tim Graham]

To authors of third-party database backends,

We'd like to start documenting changes to the database backend API [1], but 
we need some help with this.

First, please introduce yourself and which backend you maintain so we know 
of your existence.

Second, we'd like to know if you attempt to support multiple versions of 
Django in a particular release of your backend? This will help us to decide 
whether or not try to document the changes in a backwards and forwards 
compatible way.

Third, could you try updating your backend to 1.8 and let us know what 
problems you run into so we know what documentation to add?

The section of the release notes that will be expanded with details is: 
https://docs.djangoproject.com/en/dev/releases/1.8/#database-backend-api

Thank-you!

[1] https://code.djangoproject.com/ticket/24106

-- 
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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a9c2aefc-f6f0-46db-804a-3608d033017c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.