Skip to main content

djangobible python library.

Project description

djangobible

The djangobible library is a Django app that wraps the pythonbible library and provides models, managers, and other tools to easily index an object by a scripture reference.

Latest Version
License
Tests
Code Quality
Supported Python/Django Versions

Attempted to test with Python 3.13, but the testing framework has a dependency that has not yet been updated to work with Python 3.13.

Installation

Pip install the djangobible library.

pip install djangobible

Add djangobible to your Django project's INSTALLED_APPS setting:

INSTALLED_APPS = [
    ...,  # other apps
    "djangobible",
]

Run the django migrations for djangobible

./manage.py migrate djangobible

Settings

There currently are no settings (other than INSTALLED_APPS) related to the djangobible project. In the future, it would be nice to have settings that determine things like the available versions of the Bible and the default version.

Also, once support is implemented for multiple locales and languages, there could be related settings for that functionality.

Features

The djangobible library is a complete wrapper for the pythonbible library, so importing the djangobible library as:

import djangobible as bible

will provide all the same functionality as importing the pythonbible library as:

import pythonbible as bible

This includes features such as:

  • Searching text for Scripture references
  • Converting a normalized scripture reference into a list of integer verse ids
  • Converting a list of verse id integers into a list of normalized scripture references
  • Converting a list of normalized scripture references into a formatted string scripture reference
  • Retrieving the Biblical text (in one or more open-source or public domain versions) for a given verse ID integer

For more information, see the pythonbible documentation.

In addition, the djangobible library includes the following features:

Template Tags

There are currently two template tags provided by the djangobible library: verse_reference and verse_text.

verse_reference

The verse_reference template tag, given a verse ID and a Bible version, returns the appropriate Scripture reference string.

For example, given verse_id = 1001001 and version = djangobible.Version.KING_JAMES, the following snippet from a Django template:

{% load verse_tags %}
...
{% verse_reference verse_id version=version %}

would display:

Genesis 1:1

The version parameter is optional, and the current default is King James, though that will ideally be configurable in the future.

There is another optional parameter, full_title, which is a boolean flag to determine whether to display the long version or the short version of the book of the Bible title. It defaults to False, which displays the short version. For example, given verse_id = 1001001 and version = djangobible.Version.KING_JAMES and full_title = True, the following snippet from a Django template:

{% load verse_tags %}
...
{% verse_reference verse_id version=version full_title=full_title %}

would display:

The First Book of Moses, called Genesis 1:1

verse_text

The verse_text template tag, given a verse ID and a Bible version, returns the appropriate text of that Bible verse.

For example, given verse_id = 1001001 and version = djangobible.Version.KING_JAMES, the following snippet from a Django template:

{% load verse_tags %}
...
{% verse_text verse_id %}

would display:

In the beginning God created the heaven and the earth.

The version parameter is optional, and the current default is King James, though that will ideally be configurable in the future.

One-to-many style relationships between verses and Django models

For situations where an instance of a Django model needs to be associated with a single verse, that Django model can have a field of type VerseField.

For example:

from django.db import models

import djangobible as bible


class MyModel(models.Model):
    ...  # other fields

    verse = bible.VerseField()

The underlying implementation of VerseField is an IntegerField which stores the verse ID of the associated verse.

Having this custom field type provides several benefits:

  • The Django admin (and Wagtail) form contains a text field for the verse rather than an integer field and allows the user to enter the Scripture reference text rather than the verse id, which they may not know. It then validates that text to ensure it references one, and only one, verse.
  • As just mentioned, this allows for validation, not only that the value is one, and only one, verse id, but that it is also a valid verse id (i.e. that it represents a book, chapter, and verse of the Bible that actually exists).
  • More readable query filters (e.g. MyModel.objects.filter(verse=1001001) is valid, but so is MyModel.objects.filter(verse="Genesis 1:1")).

You can set the verse field with either the int verse ID or the string reference:

my_object = MyModel.objects.create(name="my object")
my_object.verse = 1001001
my_object.save()

or

my_object = MyModel.objects.create(name="my object")
my_object.verse = "Genesis 1:1"
my_object.save()

You can filter the objects in the query set by either the int verse ID or the string reference:

MyModel.objects.filter(verse=1001001)

or

MyModel.objects.filter(verse="Genesis 1:1")

In any of the above examples, if the verse is not a valid verse ID integer or string reference for a single verse, then a ValidationError will be raised.

Many-to-many style relationships between verses and Django models

WARNING: This is still a work in progress, and this functionality does not yet exist in a stable form.

There are situations where an instance of a Django model needs to be associated with multiple verses. The current intended solution, inspired by the django-taggit library, is to implement this feature in such a way that you would add this relationship to your model like:

from django.db import models

import djangobible as bible


class MyModel(models.Model):
    ...  # other fields

    verses = bible.VerseManager()

Then you could add, remove, and reference those verses with something like:

>>> my_object = MyModel.objects.create(name="My Object")
>>> my_object.verses.add("Genesis 1:1-3")
>>> my_object.verses.all()
[<Verse: Genesis 1:1>, <Verse: Genesis 1:2>, <Verse: Genesis 1:3>]
>>> my_object.verses.remove("Genesis 1:2")
>>> my_object.verses.all()
[<Verse: Genesis 1:1>, <Verse: Genesis 1:3>]
>>> MyModel.objects.filter(verses__in=[1001001])
[<MyModel: My Object>]

Ideally, the form field would be a text field where the user could enter a list of Scripture references (e.g. "Genesis 1:1,3-10;Psalm 119;Luke 2:1-18;John 3:16")

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

djangobible-0.2.1.tar.gz (24.7 kB view details)

Uploaded Source

Built Distribution

djangobible-0.2.1-py3-none-any.whl (9.8 kB view details)

Uploaded Python 3

File details

Details for the file djangobible-0.2.1.tar.gz.

File metadata

  • Download URL: djangobible-0.2.1.tar.gz
  • Upload date:
  • Size: 24.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: python-requests/2.29.0

File hashes

Hashes for djangobible-0.2.1.tar.gz
Algorithm Hash digest
SHA256 d19414ecb920d1b61a56ecb20c423fbc8e2e1c0508caddd8ae13eb533e39f742
MD5 103763e38d6abdd9511f675d5d7021fe
BLAKE2b-256 2d8b5cc4c4bf8f70b735dbdf5faa5866d554024683efbfba65b6bee13a5aff1d

See more details on using hashes here.

File details

Details for the file djangobible-0.2.1-py3-none-any.whl.

File metadata

File hashes

Hashes for djangobible-0.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 0962d05b6f65a6b051afb5520c3d82ef9eeebd6f3ead5bafc0a1875182880353
MD5 f7b1cd173bcba2ee50521ecad589fea1
BLAKE2b-256 283fe8a8713b2dcdb4df9db274dc59ccdaaee45d37b934e1970c5a830d0415ac

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page