On Sat, Jul 04, 2009 at 11:02:32AM +0200, Josselin Mouette wrote:
> 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.
The problem is that while they are data files, they really are used at
runtime as python modules generated dynamically. So they must belong
to some parent module, which upstream grants to exist via that (empty)
__init__.py
> > 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.
JFTR, here is a nicer solution we agreed upon on #debian-python: add a
comment to the incriminated __init__.py file(s): that way they do not
get removed by pysupport.
In the interim, that is a cleaner work-around.
Thanks,
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
