Meaningless is a Python library used to retrieve, process and download Bible passages from Bible Gateway.
Features include:
Now accepting feature requests! If you want to see a certain feature included, please create an issue describing all the necessary details.
pip install meaningless
Documentation is generated using Sphinx.
The API documentation is hosted through GitHub Pages at the following link: https://daniel-tran.github.io/meaningless/
You can view the API documentation as static HTML documents from docs\index.html. After cloning this repo, you can load the HTML files in a web browser, which allows you to navigate to other sections.
The Web Extractor is used to obtain passage information directly from Bible Gateway.
from meaningless import WebExtractor
if __name__ == '__main__':
bible = WebExtractor()
passage = bible.get_passage('Ecclesiastes', 1, 2)
print(passage)
Output:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
The YAML Downloader is which formats passages obtained from the Bible Gateway website (using the Web Extractor) into a YAML structure and writes it out to a file:
from meaningless import YAMLDownloader
if __name__ == '__main__':
downloader = YAMLDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
Output:
Running the above code would produce a file called Ecclesiastes.yaml in the current working directory with the approximate contents:
Ecclesiastes:
1:
2: "² “Meaningless! Meaningless!”\n says the Teacher.\n“Utterly meaningless!\n\
\ Everything is meaningless.”"
Info:
Language: English
Translation: NIV
Timestamp: '0000-00-00T00:00:00.000000+00:00'
Meaningless: 0.0.0
The YAML Extractor uses the generated files from the YAML Downloader to find passages. This is faster than the Web Extractor, since it is not retrieving information from the Internet and is also unaffected by bandwidth limitations.
from meaningless import YAMLExtractor
if __name__ == '__main__':
bible = YAMLExtractor()
passage = bible.get_passage('Ecclesiastes', 1, 2)
print(passage)
Output:
Assuming the YAML downloader has already generated a YAML file in the current directory called Ecclesiastes.yaml which contains the book of Ecclesiastes in YAML format:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
The YAML File Interface is a set of helper methods used to read and write YAML files. This can be useful if you need to do some customised processing on a downloaded YAML file.
from meaningless import YAMLDownloader, yaml_file_interface
if __name__ == '__main__':
downloader = YAMLDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
bible = yaml_file_interface.read('./Ecclesiastes.yaml')
bible['Info']['Customised?'] = True
yaml_file_interface.write('./Ecclesiastes.yaml', bible)
Output:
Running the above code would produce a file called Ecclesiastes.yaml in the current working directory with the approximate contents:
Ecclesiastes:
1:
2: "² “Meaningless! Meaningless!”\n says the Teacher.\n“Utterly meaningless!\n\
\ Everything is meaningless.”"
Info:
Language: English
Translation: NIV
Timestamp: '0000-00-00T00:00:00.000000+00:00'
Meaningless: 0.0.0
Customised?: true
The JSON Downloader is effectively the same as the YAML Downloader except the resulting file is in JSON format and has a different file extension.
from meaningless import JSONDownloader
if __name__ == '__main__':
downloader = JSONDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
Output:
Running the above code would produce a file called Ecclesiastes.json in the current working directory with the approximate contents:
{
"Ecclesiastes": {
"1": {
"2": "² “Meaningless! Meaningless!”\n says the Teacher.\n“Utterly meaningless!\n Everything is meaningless.”"
}
},
"Info": {
"Language": "English",
"Meaningless": "0.0.0",
"Timestamp": "0000-00-00T00:00:00.000000+00:00",
"Translation": "NIV"
}
}
Much like the YAML Extractor, the JSON Extractor uses the generated files from the JSON Downloader to find passages.
from meaningless import JSONExtractor
if __name__ == '__main__':
bible = JSONExtractor()
passage = bible.get_passage('Ecclesiastes', 1, 2)
print(passage)
Output:
Assuming the JSON downloader has already generated a JSON file in the current directory called Ecclesiastes.json which contains the book of Ecclesiastes in JSON format:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
The JSON File Interface is a set of helper methods used to read and write JSON files. Similar to the YAML File Interface, it can be used to do customised processing on a JSON file or its contents.
from meaningless import JSONDownloader, json_file_interface
if __name__ == '__main__':
downloader = JSONDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
bible = json_file_interface.read('./Ecclesiastes.json')
bible['Info']['Customised?'] = True
json_file_interface.write('./Ecclesiastes.json', bible)
Output:
Running the above code would produce a file called Ecclesiastes.json in the current working directory with the approximate contents:
{
"Ecclesiastes": {
"1": {
"2": "² “Meaningless! Meaningless!”\n says the Teacher.\n“Utterly meaningless!\n Everything is meaningless.”"
}
},
"Info": {
"Customised?": true,
"Language": "English",
"Meaningless": "0.0.0",
"Timestamp": "0000-00-00T00:00:00.000000+00:00",
"Translation": "NIV"
}
}
The XML Downloader is effectively the same as the YAML Downloader except the resulting file is in a specific XML format and has a different file extension.
from meaningless import XMLDownloader
if __name__ == '__main__':
downloader = XMLDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
Output:
Running the above code would produce a file called Ecclesiastes.xml in the current working directory with the approximate contents:
<?xml version="1.0" encoding="utf-8"?>
<root>
<info>
<language>English</language>
<translation>NIV</translation>
<timestamp>0000-00-00T00:00:00.000000+00:00</timestamp>
<meaningless>0.0.0</meaningless>
</info>
<book name="Ecclesiastes" tag="_Ecclesiastes">
<chapter number="1" tag="_1">
<passage number="2" tag="_2">² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”</passage>
</chapter>
</book>
</root>
Much like the YAML Extractor, the XML Extractor uses the generated files from the XML Downloader to find passages.
from meaningless import XMLExtractor
if __name__ == '__main__':
bible = XMLExtractor()
passage = bible.get_passage('Ecclesiastes', 1, 2)
print(passage)
Output:
Assuming the XML downloader has already generated an XML file in the current directory called Ecclesiastes.xml which contains the book of Ecclesiastes in XML format:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
The XML File Interface is a set of helper methods used to read and write XML files. Unlike the other file interfaces, this is more geared towards the specific document format used by the XML Downloader and Extractor, so you may observe some strange behaviour if you try using this for general purpose XML file interactions.
from meaningless import XMLDownloader, xml_file_interface
if __name__ == '__main__':
downloader = XMLDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
bible = xml_file_interface.read('./Ecclesiastes.xml')
bible['Info']['Customised'] = True
xml_file_interface.write('./Ecclesiastes.xml', bible)
Output:
Running the above code would produce a file called Ecclesiastes.xml in the current working directory with the approximate contents:
<?xml version="1.0" encoding="utf-8"?>
<root>
<info>
<language>English</language>
<translation>NIV</translation>
<timestamp>0000-00-00T00:00:00.000000+00:00</timestamp>
<meaningless>0.0.0</meaningless>
<customised>true</customised>
</info>
<book name="Ecclesiastes" tag="_Ecclesiastes">
<chapter number="1" tag="_1">
<passage number="2" tag="_2">² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”</passage>
</chapter>
</book>
</root>
Note that you are allowed to write badly formed XML documents using this file interface, but they will cause runtime errors in your code upon trying to read and process them.
The CSV Downloader is effectively the same as the YAML Downloader except the resulting file is in CSV format and has a different file extension.
from meaningless import CSVDownloader
if __name__ == '__main__':
downloader = CSVDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
Output:
Running the above code would produce a file called Ecclesiastes.csv in the current working directory with the approximate contents:
Book,Chapter,Passage,Text,Language,Translation,Timestamp,Meaningless
Ecclesiastes,1,2,"² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”",English,NIV,0000-00-00T00:00:00.000000+00:00,0.0.0
Much like the YAML Extractor, the CSV Extractor uses the generated files from the CSV Downloader to find passages.
from meaningless import CSVExtractor
if __name__ == '__main__':
bible = CSVExtractor()
passage = bible.get_passage('Ecclesiastes', 1, 2)
print(passage)
Output:
Assuming the CSV downloader has already generated a CSV file in the current directory called Ecclesiastes.csv which contains the book of Ecclesiastes in CSV format:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
The CSV File Interface is a set of helper methods used to read and write CSV files. This is geared towards the CSV document format used by the CSV Downloader and Extractor and cannot be used to add custom attributes to the output file when writing CSV data.
from meaningless import CSVDownloader, csv_file_interface
if __name__ == '__main__':
downloader = CSVDownloader()
downloader.download_passage('Ecclesiastes', 1, 2)
bible = csv_file_interface.read('./Ecclesiastes.csv')
bible['Info']['Language'] = 'English (EN)'
csv_file_interface.write('./Ecclesiastes.csv', bible)
Output:
Running the above code would produce a file called Ecclesiastes.csv in the current working directory with the approximate contents:
Book,Chapter,Passage,Text,Language,Translation,Timestamp,Meaningless
Ecclesiastes,1,2,"² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”",English (EN),NIV,0000-00-00T00:00:00.000000+00:00,0.0.0
All file-based extractors support passage filtering by search text or by regular expression.
The section below is a simple example that prints passages containing "meaningless" from Ecclesiastes 1:
from meaningless import YAMLDownloader, YAMLExtractor
if __name__ == '__main__':
downloader = YAMLDownloader()
downloader.download_chapter('Ecclesiastes', 1)
bible = YAMLExtractor()
print(bible.find_text_in_chapter('meaningless', 'Ecclesiastes', 1))
Output:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
¹⁴ I have seen all the things that are done under the sun; all of them are meaningless, a chasing after the wind.
The section below is another simple example that prints passages containing "meaningless" or "wisdom" from Ecclesiastes 1:
from meaningless import YAMLDownloader, YAMLExtractor
if __name__ == '__main__':
downloader = YAMLDownloader()
downloader.download_chapter('Ecclesiastes', 1)
bible = YAMLExtractor()
print(bible.find_text_in_chapter('meaningless|wisdom', 'Ecclesiastes', 1, is_regex=True))
Output:
² “Meaningless! Meaningless!”
says the Teacher.
“Utterly meaningless!
Everything is meaningless.”
¹³ I applied my mind to study and to explore by wisdom all that is done under the heavens. What a heavy burden God has laid on mankind!
¹⁴ I have seen all the things that are done under the sun; all of them are meaningless, a chasing after the wind.
¹⁶ I said to myself, “Look, I have increased in wisdom more than anyone who has ruled over Jerusalem before me; I have experienced much of wisdom and knowledge.”
¹⁷ Then I applied myself to the understanding of wisdom, and also of madness and folly, but I learned that this, too, is a chasing after the wind.
¹⁸ For with much wisdom comes much sorrow;
the more knowledge, the more grief.
To report bugs and other problems, create an issue in this repo that details:
If you have any questions, complaints, compliments or even ideas to improve this library, you can also leave them as a GitHub issue with the appropriate label. Or you can also send an email to dantran.au@gmail.com, although a response will likely take longer than replying to a GitHub issue.
This is NOT recommended under normal circumstances, as it may cause problems with the library API when using the modified file.
The Base Extractor and Downloader all use the same overall structure to represent passage contents for all translations.
For the Web Extractor, the page structure of the Bible Gateway site is mostly the same across different translations, so as long as the translation-specific differences are handled correctly, the same set of unit tests should suffice.
Short answer: It depends.
The primary case for dropping support for a certain Bible translation is if there is an observed problem in the extracted Bible contents which is considerably difficult to address due to how the Biblical contents is structured (in terms of HTML) on the Bible Gateway site. With that in mind, reinstating support for Bible translations can be reconsidered when such problems subside.
Without having to go through every single passage and check if it is omitted, a set of common omitted passages are found here:
These passages are checked on the Bible Gateway site, and then added to the Base Downloader's internal list of omitted passages for the relevant translation.
If you notice any problems such as unhandled omitted passages or incorrect tagging of an omitted passage in the Base Downloader, please create an issue to report it.
At the moment, you can use the Web Extractor's search(), search_multiple() and other related functions to obtain passages from the Apocrypha books.
There is currently no official support for the Apocrypha books in the other downloaders and extractors, at least until the issues identified here become easier to work around.
To make a contribution to this library, refer to CONTRIBUTING.md.
This library is not endorsed by nor affiliated with Bible Gateway or any of its partners.
get_passage_range in the Web Extractor would incorrectly cap the upper limit of passages to 100use_legacy_mode flag in the XML Downloader and Extractoruse_legacy_mode flag to XML Downloader and Extractor to continue using the original behaviour and assist with transitioning to the updated XML file interfaceFAQs
Retrieves, processes and downloads Bible passages from Bible Gateway
We found that meaningless demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.