Change project_edit to not use generic views

Bug #902200 reported by Guilherme Salgado
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Offspring
Triaged
High
Unassigned

Bug Description

There's a bug (https://code.djangoproject.com/ticket/17021) in Django's generic views that won't be fixed because function-based generic views are deprecated, so we should change that view to no longer use them, avoiding the nasty hack we need now.

Alternatively, we could update to a version of Django that provides class based generic views, as those are supposed to not be affected by that bug.

Changed in offspring:
assignee: nobody → Guilherme Salgado (salgado)
status: New → Triaged
importance: Undecided → High
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

Can you explain what the nasty hack is? I don't think we're experiencing this problem with our deployment of Offspring.

Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

I think migrating to Django 1.3 to fix this problem is quite a leap, though we have talked about the need to move to a newer version of Django for more general reasons. Is there something tactical we can do here in the interim?

affects: offspring → linaro-offspring
Revision history for this message
Guilherme Salgado (salgado) wrote :

It no longer affects trunk as it was part of the changes that introduced private projects, which have been reverted

Changed in linaro-offspring:
assignee: Guilherme Salgado (salgado) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.