DQA
Installation
To install with pypi, use:
pip install dqa
Quick Start
Open file config.ini and set the following parameters: LOG_FILE_PATH and
OUTPUT_DIR for your environment. Next, open file example.py and change file_path to point to your
(context) document. Note that this version currently only supports .docx files.
If you want to pose predefined questions, set questions in config.ini to your list of questions:
questions = ['What is the subject?', 'Who bought the food?']
If you want to pose questions interactively, set questions in config.ini to None:
questions = None
To run example.py, use:
python example.py
Metadata
Release files for dqa 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dqa-0.2-py3-none-any.whl | Python 3 | none | any | Details for dqa-0.2-py3-none-any.whl |
Release files / dqa-0.2-py3-none-any.whl
| Download URL | dqa-0.2-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
671c21178b53ed53e6598687cb1b30cea0adb34997f5e62c406254df9c3bb547
|
|
BLAKE2b-256 checksum How to use checksums |
5cd0b5adc4143009341f4a5ff82afb19a93c061f0791fda8cbc5cbaeeea3e7f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.5.0 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.7
|
Security for dqa 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.