Bug#632217: python-django: empty __init__.py files not packaged, modules can't be imported
Package: python-django Version: 1.3-2 Severity: grave Justification: renders package unusable The python-django package omits all __init__.py files that are 0-sized. The django upstream sources contain a lot of such files. These missing files lead to many django modules not being available, because python expects module directories to contain a __init__.py file. How to reproduce: python -c 'import django.core' Expected result: No error Actual result: Traceback (most recent call last): File string, line 1, in module ImportError: No module named core Solution: Package even 0-sized files. NB: python-openid has the same problem in extesions/draft. Problem also presents for squeeze package versions. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable'), (300, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-238.12.1.el5.028stab091.1 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-django depends on: ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-support 1.0.10 automated rebuilding support for P Versions of packages python-django recommends: ii libjs-jquery 1.4.2-2JavaScript library for dynamic web Versions of packages python-django suggests: ii python-flup 1.0.2-1Implements Python Web Server Gatew pn python-mysqldbnone (no description available) pn python-psycopgnone (no description available) pn python-psycopg2 none (no description available) ii python-sqlite 1.0.1-7+b1 python interface to SQLite 2 pn python-yaml none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632217: python-django: empty __init__.py files not packaged, modules can't be imported
On Fri, 01 Jul 2011, Simon Schubert wrote: On 06/30/2011 10:50 PM, Raphael Hertzog wrote: On Thu, 30 Jun 2011, Simon Schubert wrote: The python-django package omits all __init__.py files that are 0-sized. The django upstream sources contain a lot of such files. These missing files lead to many django modules not being available, because python expects module directories to contain a __init__.py file. Yes, this is on purpose, they are removed by python-support at build time and they are recreated by python-support at install time. Fair enough. This does not happen for me on install time. I have to run update-python-modules -f manually. Is this intended? No it's not intended but I don't see how that could be possible. Can you show the output of aptitude reinstall python-django ? Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
