Le vendredi 03 juillet 2009 à 18:36 +0200, Stefano Zacchiroli a écrit : > To ensure "tw.forms.templates" is a valid module, upstream ships a > __init__.py file in that dir. But when that dir gets handled by > update-python-modules, the __init__.py file is removed, on the > assumption that not containing any *.py (or *.so) files, that dir > should not be a module. > > While that is probably a sane default behaviour (to work around many > dump upstreams which put __init__.py everywhere), in this particular > case I need a way to tell update-python-modules that that dir should > really be mapped to the module namespace. With the current > implementation, I did not find the way to do that, hence I'm filing a > wishlist request about it
Gosh, those Python developers really invent new dirty tricks every day. My primary recommendation would be to move those data files to a directory in /usr/share and patch the code to use this place, instead of adding another hack on top of such a bad idea. > My current (horrible) work around is to touch a dummy and empty .py > file in the appropriate dir before the build start. Please get me away > from such hack :) Well, it looks like a hack, but I was going to recommend you to do this. Any other solution would look the same in the end, and it is really harmless. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
