On Sunday, 16 Jul 2017 at 15:24 UTC
Guido Günther wrote:
> Hi,
> On Sun, Jul 16, 2017 at 05:12:28PM +0200, Manolo Díaz wrote:
> > On Sunday, 16 Jul 2017 at 11:27 UTC
> > Guido Günther wrote:
> >
> > > Hi,
> > > On Sun, Jul 16, 2017 at 11:22:47AM +0200, Manolo Díaz wrote:
> > > > On Sunday, 16 Jul 2017 at 09:05 UTC
> > > > Guido Günther wrote:
> > > >
> > > > > Hi,
> > > > > control: affects -1 calibre
> > > >
> > > > [...]
> > > >
> > > > > Starts here without problems. Does
> > > > >
> > > > > python -c "from six.moves import _thread"
> > > > >
> > > > > work for you? If it does not work your python-six is broken. Maybe you
> > > > > have a local version of six lying around?
> > > > > Cheers,
> > > > > -- Guido
> > > >
> > > > Hi,
> > > >
> > > > python -c "from six.moves import _thread" does apparently nothing and
> > > > exits with 0. Is this expected?
> > > >
> > >
> > > Yept. That's how it should be.
> > >
> > > > The version of python-six on my system is 1.10.0-4 (current testing)
> > > > and if it was broken I think calibre wouldn't start with only
> > > > downgrading python-dateutil.
> > >
> > > It might because the old python-dateutil version might not have used it.
> > > Can you do a
> > >
> > > strace -f -s2048 /usr/bin/calibre
> > >
> > > and attach this to the bugreport please.
> > > Cheers,
> > > -- Guido
> >
> > Of course. It's attached.
>
> You have six.pyc in the calibre directory that's tripping up things:
>
> open("/usr/lib/calibre/six.pyc", O_RDONLY) = 9
>
> can you remove that and try again?
> Cheers,
> -- Guido
It works. After removing /usr/lib/calibre/six.pyc calibre works again.
So you are right, it's not a python-datetime bug.
Thank you.
Regards,
--
Manolo Díaz
