On 0, Bernd Zeimetz <b...@debian.org> wrote:
> David Aguilar wrote:
> >
> > Thanks Bernd.
> > What should I do about the .pyc/.pyo files?
> >
> > I'm assuming that I shouldn't generate them and should instead
> > let Debian generate them?
>
> Right, that's what python-support (and python-central, if you like that more)
> takes care of.
> They'll also take care of your .py files in /usr/share/packagename
> automatically, so if you install the modules to
> $(CURDIR)/debian/usr/share/packagename, everything should be fine. You need to
> make sure that the files in /usr/bin know about the path, though, for example
> by
> adding the path to sys.path.
Awesome, okay I'll work on getting this fixed soon.
I've cc'd cola's debian package maintainer in case there's
anything that needs to be done on the packaging front to
account for the path change from using
/usr/lib/python2.*/site-packages/cola to
/usr/share/cola/lib for cola's private modules.
BTW I have a fix for the bug regarding cola breaking
help('modules') so I'll probably be rolling a new release
tonight to address it.
Thanks for the help!
--
David
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
