Move django from parts and install it as egg

Bug #784543 reported by Mantas Zimnickas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Django Recipe
Fix Committed
Medium
Unassigned

Bug Description

Why Django is not installed as egg, but instead added to parts?

This leads to dependency checking errors if a package requires django...

In other words, for other packages it is not possible to check if django is installed, because it is simply added to parts and to pythonpath.

Revision history for this message
Mantas Zimnickas (sirex) wrote :
Revision history for this message
roland (roland-micite) wrote :

Thank you for reporting this bug.

This is currently not supported. If you have a patch/tests I'm more than willing to accept it.
Meanwhile I'll look into it.

Changed in djangorecipe:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
roland (roland-micite) wrote :

A quick update:

This was fixed in 0.20, see https://bugs.launchpad.net/djangorecipe/+bug/397864.
It installs django as a development egg.

Revision history for this message
roland (roland-micite) wrote :

The new djangorecipe release has undergone a major code cleanup. Django is now installed as a real egg. This issue should therefor be resolved.

Please test.

Changed in djangorecipe:
status: Confirmed → Fix Committed
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.