← Back to team overview

openlp-core team mailing list archive

Re: [Bug 652380] Re: OpenLP1.x database fails to import in 1.9.3 with character issues

 

My guess is that it is more of a exotic Python memory management error that
occurs on W7 64bit.  A little more experimenting showed that moving the
import sqlite into the openlp\core\lib\pluginmanager prevents the error
which looks like a memory management problem.  The  both pythonpath and path
are the same regardless of where the import sqlite occurs in openlp.  It
just seems necessary to have sqlite imported before the test for presence is
made.  Of course this may be restricted to my machine, I don't have access
to another W7 64bit.

Albert Steiner

On Sun, Jan 2, 2011 at 11:58 AM, m2j <652380@xxxxxxxxxxxxxxxxxx> wrote:

> So this is a error, which has nothing in common with this bug except of
> the fact, that it also effects the openlp.org 1.x importer. This bug is
> called “... fails to import ... with character issues”. The problem
> seems to be, that the environment path for the include directory does
> not link to the right directory. A packaging issue. I will hint Raoul
> onto this topic.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/652380
>
> Title:
>  OpenLP1.x database fails to import in 1.9.3 with character issues
>
> Status in OpenLP - Worship Presentation Software:
>  Fix Released
>
> Bug description:
>  Tried to import our church database into 1.9.3 and it failed on the 5th
> song with encoding problems in copyright field.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/openlp/+bug/652380/+subscribe
>


-- 
Albert Steiner

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/652380

Title:
  OpenLP1.x database fails to import in 1.9.3 with character issues

Status in OpenLP - Worship Presentation Software:
  Fix Released

Bug description:
  Tried to import our church database into 1.9.3 and it failed on the 5th song with encoding problems in copyright field.





Follow ups

References