Le dimanche 06 janvier 2008 à 19:58 +0100, Piotr Ożarowski a écrit : > Package: python-support > Version: 0.7 > Severity: normal > > Please add a possibility to disable changes introduced in 0.7 (adding > __init__.py files in empty directories) > > It should be disabled by default (IMHO) otherwise more bugs like #459446 > will occur
Let me guess: there is a templates.py containing the module, and a a templates/ subdirectory containing templates? Frankly, it is expected, when doing such horrible things, to hit horrible bugs. Python templates, in a directory available to python, that you don’t want available to the interpreter? Are upstream developers mad or what? Python directories are meant to put python packages, not tons of data and whatnot for the package, and it is a real shame there are facilities in the language to help doing such stupid things. This data should have been in /usr/share/something instead from the very beginning. Given how namespace packages are implemented, you can’t disable them on a per-package basis. What we could imagine is to ship e.g. a “.noinit” file in directories in which you don’t want __init__.py to be created. But this should be a workaround for buggy packages, not the default behavior. Would that solution be sufficient for you? Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
