explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2024-09-22 20:09:18 +03:00
Code Issues Packages Projects Releases Wiki Activity
e6526b0831
spaCy/spacy/lang/es/tokenizer_exceptions.py

84 lines
1.4 KiB
Python
Raw Normal View History

Tidy up and move noun_chunks, token_match, url_match
2020-07-22 23:18:46 +03:00
from ..tokenizer_exceptions import BASE_EXCEPTIONS
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
from ...symbols import ORTH, NORM
Tidy up and move noun_chunks, token_match, url_match
2020-07-22 23:18:46 +03:00
from ...util import update_exc
Reorganise language data
2016-12-18 18:54:19 +03:00
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
_exc = {
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
"pal": [{ORTH: "pa"}, {ORTH: "l", NORM: "el"}],
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
}
Update tokenizer exceptions for Spanish
2016-12-21 20:06:17 +03:00
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
for exc_data in [
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
{ORTH: "n°"},
{ORTH: "°C"},
{ORTH: "aprox."},
{ORTH: "dna."},
{ORTH: "dpto."},
{ORTH: "ej."},
{ORTH: "esq."},
{ORTH: "pág."},
{ORTH: "p.ej."},
{ORTH: "Ud.", NORM: "usted"},
{ORTH: "Vd.", NORM: "usted"},
{ORTH: "Uds.", NORM: "ustedes"},
{ORTH: "Vds.", NORM: "ustedes"},
Spanish tokenizer exception and examples improvement (#5531) * Spanish tokenizer exception additions. Added Spanish question examples * erased slang tokenization examples
2020-06-01 19:18:34 +03:00
{ORTH: "vol.", NORM: "volúmen"},
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
]:
Tidy up tokenizer exceptions
2017-11-02 01:02:45 +03:00
_exc[exc_data[ORTH]] = [exc_data]
Update tokenizer exceptions for Spanish
2016-12-21 20:06:17 +03:00
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
# Times
Update tokenizer exceptions for Spanish
2016-12-21 20:06:17 +03:00
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
_exc["12m."] = [{ORTH: "12"}, {ORTH: "m."}]
Update tokenizer exceptions for Spanish
2016-12-21 20:06:17 +03:00
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
for h in range(1, 12 + 1):
for period in ["a.m.", "am"]:
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
_exc[f"{h}{period}"] = [{ORTH: f"{h}"}, {ORTH: period}]
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
for period in ["p.m.", "pm"]:
Remove POS, TAG and LEMMA from tokenizer exceptions
2020-07-23 00:09:01 +03:00
_exc[f"{h}{period}"] = [{ORTH: f"{h}"}, {ORTH: period}]
Update tokenizer exceptions for Spanish
2016-12-21 20:06:17 +03:00
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
for orth in [
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"a.C.",
"a.J.C.",
Spanish tokenizer exception and examples improvement (#5531) * Spanish tokenizer exception additions. Added Spanish question examples * erased slang tokenization examples
2020-06-01 19:18:34 +03:00
"d.C.",
"d.J.C.",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"apdo.",
"Av.",
"Avda.",
"Cía.",
Spanish tokenizer exception and examples improvement (#5531) * Spanish tokenizer exception additions. Added Spanish question examples * erased slang tokenization examples
2020-06-01 19:18:34 +03:00
"Dr.",
"Dra.",
Improve tokenization for UD Spanish AnCora (#5253)
2020-04-06 14:18:23 +03:00
"EE.UU.",
Update tokenizer_exceptions.py See https://github.com/explosion/spaCy/pull/6643
2020-12-29 15:05:11 +03:00
"Ee.Uu.",
Add full exceptions with spaces
2021-01-29 16:27:22 +03:00
"EE. UU.",
"Ee. Uu.",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"etc.",
Improve tokenization for UD Spanish AnCora (#5253)
2020-04-06 14:18:23 +03:00
"fig.",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"Gob.",
"Gral.",
"Ing.",
"J.C.",
Improve tokenization for UD Spanish AnCora (#5253)
2020-04-06 14:18:23 +03:00
"km/h",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"Lic.",
"m.n.",
"núm.",
"P.D.",
"Prof.",
"Profa.",
"q.e.p.d.",
Update tokenizer_exceptions.py See https://github.com/explosion/spaCy/pull/6643
2020-12-29 15:05:11 +03:00
"Q.E.P.D.",
"S.A.",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"S.L.",
Update tokenizer_exceptions.py See https://github.com/explosion/spaCy/pull/6643
2020-12-29 15:05:11 +03:00
"S.R.L.",
"s.s.s.",
💫 Tidy up and auto-format .py files (#2983) <!--- Provide a general summary of your changes in the title. --> ## Description - [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files. - [x] Update flake8 config to exclude very large files (lemmatization tables etc.) - [x] Update code to be compatible with flake8 rules - [x] Fix various small bugs, inconsistencies and messy stuff in the language data - [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means) Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results. At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information. ### Types of change enhancement, code style ## Checklist <!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] --> - [x] I have submitted the spaCy Contributor Agreement. - [x] I ran the tests, and all new and existing tests passed. - [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
"Sr.",
"Sra.",
"Srta.",
]:
Reorganise Spanish language data
2017-05-08 16:48:04 +03:00
_exc[orth] = [{ORTH: orth}]
Reorganise language data
2016-12-18 18:54:19 +03:00
Tidy up and move noun_chunks, token_match, url_match
2020-07-22 23:18:46 +03:00
TOKENIZER_EXCEPTIONS = update_exc(BASE_EXCEPTIONS, _exc)
Reference in New Issue Copy Permalink