This release is a pre-release and may not be stable for production use.
THANK YOU FOR USING TEXTSPITTER!!
I created this little app to help me process documents from folder sets and batches. Instead of trying to determine each file type and process accordingly, I thought it would be more prudent to read file names and then route text extraction functions accordingly. Also, I was having a really difficult time getting textract/pdftotext to work because of damn Poppler. So instead of troubleshooting that whole process after 6+ hours, I figured this was more time-efficient.
This is my first python module, so I hope I did this well!
Installation
- Type
pip install TextSpitter - OPTIONAL type
pip install PyMuPDFto install the Python-MuPDF engine for better fidelity with text extraction (i.e.: maintaining correct White Spacing)- You will need to follow instructions to ensure that PyMuPDF's dependencies install to your system. There are wheels and binaries available for Windows, Linux, and MacOSX, though if you're on something weird like NetBSD/FreeBSD/specialty linux distros, you may e SOL. Fortunately, CLI options like Yum, Pkgin, Apt-Get and so forth will have packages available straight from the terminal.
- For detailed instructions, please visit here: https://github.com/rk700/PyMuPDF and maybe give those guys some kudos, because they worked their tails off.
Directions
This module is designed to run as simply as possible. Just provide the file location string data into the argument, and get your text returned to you.
from TextSpitter import TexSpitter as TS
folder_loc = 'foo/bar/'
docx_file = folder_loc + 'file_thing.docx'
pdf_file = folder_loc + 'file_thing.pdf'
text_file = folder_loc + 'file_thing.txt'
doc_tup = (docx_file, pdf_file, text_file)
raw_text_payload = [TS(filename=ele) for ele in doc_tup]
text = '\n'.join(raw_text_payload)
return text
TO DOs
- spruce up documentation
- Add stream functionality for s3-based file reading
- expand functionality to other file types
- TDB
WANT TO CONTRIBUTE!?
OH MY GOD, PLEASE DO.
Just make a pull request and add whatever you want (or fix whatever you want). I'll review and approve if everything seems good.
Thanks, everyone!
Metadata
Release files for textspitter 0.3.5a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| TextSpitter-0.3.5a4.tar.gz | 4.6 kB | Without provenance | Details for TextSpitter-0.3.5a4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| TextSpitter-0.3.5a4-py3-none-any.whl | Python 3 | none | any | Details for TextSpitter-0.3.5a4-py3-none-any.whl |
Total release size: 10.0 kB
Release files / TextSpitter-0.3.5a4.tar.gz
| Download URL | TextSpitter-0.3.5a4.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e835ef0678875d442e16f30d7172fad412eb8de88b11ca4105a00a543f1ca6c
|
|
BLAKE2b-256 checksum How to use checksums |
e227b6ee307815e32cce46c9f754252a006aa98a4ed5e360fcf74141fefeb545
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.6
|
Release files / TextSpitter-0.3.5a4-py3-none-any.whl
| Download URL | TextSpitter-0.3.5a4-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d88f6695220422b918f5a7a2c718d878197a1ebc8fa26bd36b10a04fd5dde5c
|
|
BLAKE2b-256 checksum How to use checksums |
a0ac2bbacae58bb12435fa5a31e931eb9d84c8f0dea44f0711ffd5e2305eb011
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.6
|
Security for textspitter 0.3.5a4
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.