mwsimpleedittypes
Edit diffs and type detection for Wikipedia (simple). The goal is to transform unstructured edits to Wikipedia articles into a structured summary of what actions were taken in the edit. This is a simplified version of mwedittypes, which is a structure-aware version of this library that can also detect content moves and more directly identify edit types. They generally have very high alignment but this library is almost 10x faster and has a smaller memory footprint.
Installation
You can install mwsimpleedittypes with pip:
$ pip install mwsimpleedittypes
Example
If one revision of wikitext is as follows:
{{Short description|Austrian painter}}
'''Karl Josef Aigen''' (8 October 1684 – 22 October 1762) was a landscape painter, born at Olomouc.
and a second revision of wikitext is as follows:
{{Short description|Austrian landscape painter}}
'''Karl Josef Aigen''' (8 October 1684 – 22 October 1762) was a landscape painter, born at [[Olomouc]].
The changes that happened would be:
- The addition of
landscapeto the short description template -- this would be registered as a Template change. - The changing of
Olomoucto a Wikilink. - Notably, despite this change to the template and addition of a link, the "Text" of the article has not changed.
This repository would return this in the following structure: {'Template':{'change':1}, 'Wikilink':{'insert':1}.
Basic Usage
>>> from mwsimpleedittypes import EditTypes
>>> prev_wikitext = '{{Short description|Austrian painter}}'
>>> curr_wikitext = '{{Short description|Austrian [[landscape painter]]}}'
>>> et = EditTypes(prev_wikitext, curr_wikitext, lang='en', timeout=5)
>>> et.get_diff()
{'Wikilink': {'insert': 1}, 'Template': {'change': 1}}
Development
We are happy to receive contributions though will default to keeping the code here relatively general (not overly customized to individual use-cases). Please reach out or open an issue for the changes you would like to merge so that we can discuss beforehand.
Code Summary
The code for computing diffs and running edit-type detection can be found in one file mwsimpleedittypes/differ.py.
The bulk of the library parses a wikitext document into a bag of nodes (Templates, Wikilinks, etc.). This is almost all done via the amazing mwparserfromhell library with a few tweaks:
- We use link namespace prefixes -- e.g., Category:, Image: -- to separate out categories and media from other wikilinks.
- We identify some additional media files that are transcluded via templates -- e.g., infoboxes -- or gallery tags.
- We also add some custom logic for parsing
<gallery>tags to identify nested links, etc., which otherwise are treated as text bymwparserfromhell. - We use custom logic for converting wikitext into text to best match what words show up in the text of the article.
The diffing component simply takes the symmetric difference of the nodes associated with each wikitext document to identify what has changed.
To accurately, but efficiently, describe the scale of textual changes in edits, we also use some regexes and heuristics to describe how much text was changed in an edit in the node differ. This is generally the toughest part of diffing text but because we do not need to visually describe the diff, just estimate the scale of how much changed, we can use relatively simple methods. To do this, we break down text changes into five categories and identify how much of each changed: paragraphs, sentences, words, punctuation, and whitespace.
Testing
The tests for the differ are contained within the tests directory.
They can be run via pytest.
We are not even close to full coverage yet given the numerous node types (template, text, etc.) and four actions (insert/remove/change/move) and varying languages for e.g., Text or Category/Media nodes, but we are working on expanding coverage.
Documentation
- For more background, see: https://meta.wikimedia.org/wiki/Research:Wikipedia_Edit_Types
Metadata
Release files for mwsimpleedittypes 1.2.5
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 | |
|---|---|---|---|---|
| mwsimpleedittypes-1.2.5.tar.gz | 21.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mwsimpleedittypes-1.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.3 kB
Release files / mwsimpleedittypes-1.2.5.tar.gz
| Download URL | mwsimpleedittypes-1.2.5.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b72cf90a6d14ce20b5cc8b7d4bfd621609342a4183039a4879a8b5d46861b2c7
|
|
BLAKE2b-256 checksum How to use checksums |
9790cb612c9dfccbe3dc30df51b5ff25abdb963f339d4bd4dd10d163bc231351
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.26.0 requests-toolbelt/0.9.1 urllib3/1.26.7 tqdm/4.64.0 importlib-metadata/4.8.2 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.4 CPython/3.6.7
|
Release files / mwsimpleedittypes-1.2.5-py3-none-any.whl
| Download URL | mwsimpleedittypes-1.2.5-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b36f30dc8df87670849a7add19af6ec71b4523b94fb4f06495a02882cc625eca
|
|
BLAKE2b-256 checksum How to use checksums |
7d054608f3b9da93df504c7fd06779698cba7ffaf9e34f57b383eb5adf9229a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.26.0 requests-toolbelt/0.9.1 urllib3/1.26.7 tqdm/4.64.0 importlib-metadata/4.8.2 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.4 CPython/3.6.7
|
Security for mwsimpleedittypes 1.2.5
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.