2017-09-16 18:40:15 +00:00
|
|
|
# coding: utf8
|
|
|
|
from __future__ import unicode_literals
|
|
|
|
|
2020-02-26 12:06:52 +00:00
|
|
|
from ..char_classes import LIST_ELLIPSES, LIST_ICONS, LIST_PUNCT, LIST_QUOTES
|
|
|
|
from ..char_classes import LIST_CURRENCY, CURRENCY, UNITS, PUNCT
|
2019-02-01 07:05:22 +00:00
|
|
|
from ..char_classes import CONCAT_QUOTES, ALPHA, ALPHA_LOWER, ALPHA_UPPER
|
2020-03-23 18:23:47 +00:00
|
|
|
from ..punctuation import TOKENIZER_PREFIXES as BASE_TOKENIZER_PREFIXES
|
2017-09-16 18:40:15 +00:00
|
|
|
|
|
|
|
|
2020-03-23 18:23:47 +00:00
|
|
|
_prefixes = ["``"] + BASE_TOKENIZER_PREFIXES
|
2020-02-26 12:06:52 +00:00
|
|
|
|
|
|
|
_suffixes = (
|
|
|
|
["''", "/"]
|
|
|
|
+ LIST_PUNCT
|
|
|
|
+ LIST_ELLIPSES
|
|
|
|
+ LIST_QUOTES
|
|
|
|
+ LIST_ICONS
|
|
|
|
+ [
|
|
|
|
r"(?<=[0-9])\+",
|
|
|
|
r"(?<=°[FfCcKk])\.",
|
|
|
|
r"(?<=[0-9])(?:{c})".format(c=CURRENCY),
|
|
|
|
r"(?<=[0-9])(?:{u})".format(u=UNITS),
|
|
|
|
r"(?<=[{al}{e}{p}(?:{q})])\.".format(
|
|
|
|
al=ALPHA_LOWER, e=r"%²\-\+", q=CONCAT_QUOTES, p=PUNCT
|
|
|
|
),
|
|
|
|
r"(?<=[{au}][{au}])\.".format(au=ALPHA_UPPER),
|
|
|
|
]
|
|
|
|
)
|
|
|
|
|
2019-02-01 07:05:22 +00:00
|
|
|
_quotes = CONCAT_QUOTES.replace("'", "")
|
2017-09-16 18:40:15 +00:00
|
|
|
|
💫 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 16:03:03 +00:00
|
|
|
_infixes = (
|
|
|
|
LIST_ELLIPSES
|
|
|
|
+ LIST_ICONS
|
|
|
|
+ [
|
2019-02-01 07:05:22 +00:00
|
|
|
r"(?<=[{al}])\.(?=[{au}])".format(al=ALPHA_LOWER, au=ALPHA_UPPER),
|
💫 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 16:03:03 +00:00
|
|
|
r"(?<=[{a}])[,!?](?=[{a}])".format(a=ALPHA),
|
2019-08-20 15:36:34 +00:00
|
|
|
r"(?<=[{a}])[:<>=](?=[{a}])".format(a=ALPHA),
|
💫 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 16:03:03 +00:00
|
|
|
r"(?<=[{a}]),(?=[{a}])".format(a=ALPHA),
|
2020-02-26 12:06:52 +00:00
|
|
|
r"(?<=[0-9{a}])\/(?=[0-9{a}])".format(a=ALPHA),
|
2019-02-01 07:05:22 +00:00
|
|
|
r"(?<=[{a}])([{q}\)\]\(\[])(?=[{a}])".format(a=ALPHA, q=_quotes),
|
💫 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 16:03:03 +00:00
|
|
|
r"(?<=[{a}])--(?=[{a}])".format(a=ALPHA),
|
|
|
|
r"(?<=[0-9])-(?=[0-9])",
|
|
|
|
]
|
|
|
|
)
|
2017-09-16 18:40:15 +00:00
|
|
|
|
|
|
|
|
2020-02-26 12:06:52 +00:00
|
|
|
TOKENIZER_PREFIXES = _prefixes
|
|
|
|
TOKENIZER_SUFFIXES = _suffixes
|
2017-09-16 18:40:15 +00:00
|
|
|
TOKENIZER_INFIXES = _infixes
|