openlp-core team mailing list archive

[Simon Hanna <1748719@xxxxxxxxxxxxxxxxxx>]

Hmm.. the bibles are a little messed up...

the init of a BibleDB object takes the following kwargs:

* path (path to the bible database file)
* name (name of the database, also used as file name for sqlite databases)
* file (no doc)

path and file are supposed to by Path objects, while the name is a
string.

It looks like during the migrations to the Paths, this was altered but
not to something useful.

especially the path and file look suspicious.

The cause of the actual bug is that the _setup method doesn't set
self.file which the delete method depends on.

It would be really helpful if all class attributes where defined in the
beginning of a class, so it's clear what the class supports and what
not. They don't have to be initialized there, but it should be easy to
see what attributes are available without looking through all methods in
the class searching for self.* to know what attributes are there.

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

Title:
  deleting a bible causes a traceback

Status in OpenLP:
  New

Bug description:
  Starting with no OpenLP config, when I import a couple of bibles
  during the FTW, and then delete a bible from the Library in the main
  interface I get a traceback.

  This happens in trunk

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1748719/+subscriptions