unidic-py
This is a version of UniDic packaged for use with pip.
This is based on UniDic 2.1.2, which is roughly 55MB zipped or 300MB unzipped. There are more recent versions of UniDic but they're significantly larger, which makes packaging difficult.
This package distributes only the files necessary for using UniDic with MeCab. The large files are gzipped for distribution and unzipped the first time the library is imported. It would be better for MeCab to unzip on the fly when reading from disk but it doesn't support that.
Example use with fugashi, though mecab-python3 works the same way:
import fugashi
import unidic
tagger = fugashi.Tagger('-d{}'.format(unidic.DICDIR))
# that's it!
License
The modern Japanese UniDic is available under the GPL, LGPL, or BSD license, see here or the included BSD license. UniDic is developed by NINJAL, the National Institute for Japanese Language and Linguistics.
The code in this repository is not written or maintained by NINJAL. The code is available under the MIT or WTFPL License, as you prefer.
Metadata
Release files for unidic 0.0.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 | Actions |
|---|---|---|---|---|
| unidic-0.0.1.tar.gz | 56.1 MB | Without provenance | Details for unidic-0.0.1.tar.gz |
Release files / unidic-0.0.1.tar.gz
| Download URL | unidic-0.0.1.tar.gz |
|---|---|
| Size | 56.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
798b332a44ff16a5d7269e7ffa81a1c01d6cf9f06be544b7c306438d61cb9d6f
|
|
BLAKE2b-256 checksum How to use checksums |
d08b4f7d2012174d9c854c3116edb9ab5359a8f4c8557e69ea776036fca90ac8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.8.0
|
Security for unidic 0.0.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.