Nobody has given any reason why we can't resolve this situation in unstable by removing python-pipeline. It is orphaned[1]. This will remove the conflicting package and we can close the bug.
Somebody said in this thread "However, I object to another package taking over the module name." - but the other package is already in Debian - he already missed his chance to object, and he failed to give any reasons why. I think it is wrong that one person can prevent constructive work to resolve release critical bugs like this.
Alternatively, django-pipeline could be modified to conflict with python-pipeline. This would allow closing the grave bug report, but seems wrong.