=========
A Python library to check for (and clean) profanity in strings.
##Installation
pip install profanity
##Usage
from profanity import profanity
profanity.contains_profanity("You smell like shit.")
Out: True
profanity.censor("You smell like shit.")
Out: 'You smell like !@#$.'
## Features
* Load your own wordlist, or use the bundled one.
* Censors words using standard censor characters (!@#$%), or load your own
censor characters.
* Uses a pool of censor characters to create a more natural censor string.
* Censors all instances of a given word with the same censor string - for
easy correlation.
### I love Forks, Pull Requests, and Bugs!
I wrote this to satisfy my needs. Please feel free to contribute if you have
other needs that you think others would benefit from!
Feel free to contact me: http://www.bugben.com
1 maintainer
Metadata
1 maintainer
Release files for profanity 1.1
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 | |
|---|---|---|---|---|
| profanity-1.1.tar.gz | 3.2 kB | Without provenance | Details |
Release files / profanity-1.1.tar.gz
| Download URL | profanity-1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
384d7a9d59567ec64196705838f79fdc64da943e52b2b33fe6d66fb0a417a951
|
|
BLAKE2b-256 checksum How to use checksums |
f6b407d53456462e26eee50abcae787c9380c01731ccc0b6c96233770e546989
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for profanity 1.1
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.
