A Python wrapper of the Yandex Mystem 3.0 morphological analyzer
Introduction
This module contains a wrapper for an excellent morphological analyzer for Russian language Yandex Mystem 3.0 released in June 2014. A morphological analyzer can perform lemmatization of text and derive a set of morphological attributes for each token. For more details about the algorithm see I. Segalovich «A fast morphological algorithm with unknown word guessing induced by a dictionary for a web search engine», MLMTA-2003, Las Vegas, Nevada, USA.
Python is the language of choice for many computational linguists, inlcluding those working with Russian language. The main motivation for this development was absence of any Python wrapper for the Mystem, a one of the most popular morphological analyzers for Russian language along with the PyMorphy2, the TreeTagger and AOT.
The third version of Mystem introduces several importaint improvements, most importaintly part-of-speech disambiguation. Our wrapper runs the Mystem in the mode which performs POS disambiguation.
This wrapper is open sources under LGPLv3 license. However, please consider that the Yandex Mystem is not open source and licensed under conditions of the Yandex License.
System Requrements
The wrapper works with CPython 2.6+/3.3+ and PyPy 1.9+.
The wrapper was tested on Ubuntu Linux 12.04+, Mac OSX 10.9+ and Windows 7+.
Installation
Stable version: https://pypi.python.org/pypi/pymystem3. You can install it using pip:
pip install pymystem3
Latest version: https://github.com/Digsolab/pymystem3
A Quick Example
>>> from pymystem3 import Mystem
>>> text = "Красивая мама красиво мыла раму"
>>> m = Mystem()
>>> lemmas = m.lemmatize(text)
>>> print(''.join(lemmas))
красивый мама красиво мыть рама
Issues
The current version can be considered as an alpha version, so please let us know if something does not work as expected. Please report any bugs or requests that you have using the GitHub issue tracker (https://github.com/Digsolab/pymystem3/issues)!
Metadata
Release files for pymystem3 0.1.0
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 |
|---|---|---|---|---|
| pymystem3-0.1.0.tar.gz | 18.5 kB | Without provenance | Details for pymystem3-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pymystem3-0.1.0-py2.7.egg | Legacy Egg format | - | - | Details for pymystem3-0.1.0-py2.7.egg |
Total release size: 38.3 kB
Release files / pymystem3-0.1.0.tar.gz
| Download URL | pymystem3-0.1.0.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e4b71ba537d1cc82adb5836843b083e19035e049a0a59f53ff62c8138090550
|
|
BLAKE2b-256 checksum How to use checksums |
954ae96136984d40ef4db56be953bba02c99f0265fc6c16594bffb4a61721a60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pymystem3-0.1.0-py2.7.egg
| Download URL | pymystem3-0.1.0-py2.7.egg |
|---|---|
| Size | 19.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
864045321b77084590dc3c4ecb6c15a5f8a1b3b9c8ffd3b845a40b9db3876dd5
|
|
BLAKE2b-256 checksum How to use checksums |
1f2df0e4c909a70c2dd551bcdb57b48a65a5d2b206683eb25703b1deac2e75b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pymystem3 0.1.0
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.