2020-07-22 23:18:46 +03:00
|
|
|
from typing import Union, Iterator, Optional, List, Tuple
|
2017-06-02 20:09:58 +03:00
|
|
|
|
|
|
|
from ...symbols import NOUN, PROPN, PRON, VERB, AUX
|
2020-05-14 13:58:06 +03:00
|
|
|
from ...errors import Errors
|
2020-07-22 23:18:46 +03:00
|
|
|
from ...tokens import Doc, Span, Token
|
2017-06-02 20:09:58 +03:00
|
|
|
|
|
|
|
|
2020-07-22 23:18:46 +03:00
|
|
|
def noun_chunks(doclike: Union[Doc, Span]) -> Iterator[Span]:
|
|
|
|
"""Detect base noun phrases from a dependency parse. Works on Doc and Span."""
|
2020-05-21 16:17:39 +03:00
|
|
|
doc = doclike.doc
|
2020-05-14 13:58:06 +03:00
|
|
|
if not doc.is_parsed:
|
|
|
|
raise ValueError(Errors.E029)
|
2018-03-27 20:23:02 +03:00
|
|
|
if not len(doc):
|
|
|
|
return
|
💫 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
|
|
|
np_label = doc.vocab.strings.add("NP")
|
|
|
|
left_labels = ["det", "fixed", "neg"] # ['nunmod', 'det', 'appos', 'fixed']
|
|
|
|
right_labels = ["flat", "fixed", "compound", "neg"]
|
|
|
|
stop_labels = ["punct"]
|
2018-03-27 20:23:02 +03:00
|
|
|
np_left_deps = [doc.vocab.strings.add(label) for label in left_labels]
|
|
|
|
np_right_deps = [doc.vocab.strings.add(label) for label in right_labels]
|
|
|
|
stop_deps = [doc.vocab.strings.add(label) for label in stop_labels]
|
2020-08-03 14:53:15 +03:00
|
|
|
for token in doclike:
|
2017-06-02 20:09:58 +03:00
|
|
|
if token.pos in [PROPN, NOUN, PRON]:
|
💫 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
|
|
|
left, right = noun_bounds(
|
|
|
|
doc, token, np_left_deps, np_right_deps, stop_deps
|
|
|
|
)
|
|
|
|
yield left.i, right.i + 1, np_label
|
2017-06-02 20:09:58 +03:00
|
|
|
token = right
|
|
|
|
token = next_token(token)
|
|
|
|
|
|
|
|
|
2020-07-22 23:18:46 +03:00
|
|
|
def is_verb_token(token: Token) -> bool:
|
2017-06-02 20:09:58 +03:00
|
|
|
return token.pos in [VERB, AUX]
|
|
|
|
|
|
|
|
|
2020-07-22 23:18:46 +03:00
|
|
|
def next_token(token: Token) -> Optional[Token]:
|
2017-06-02 20:09:58 +03:00
|
|
|
try:
|
|
|
|
return token.nbor()
|
💫 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
|
|
|
except IndexError:
|
2017-06-02 20:09:58 +03:00
|
|
|
return None
|
|
|
|
|
|
|
|
|
2020-07-22 23:18:46 +03:00
|
|
|
def noun_bounds(
|
|
|
|
doc: Doc,
|
|
|
|
root: Token,
|
|
|
|
np_left_deps: List[str],
|
|
|
|
np_right_deps: List[str],
|
|
|
|
stop_deps: List[str],
|
|
|
|
) -> Tuple[Token, Token]:
|
2017-06-02 20:09:58 +03:00
|
|
|
left_bound = root
|
|
|
|
for token in reversed(list(root.lefts)):
|
|
|
|
if token.dep in np_left_deps:
|
|
|
|
left_bound = token
|
|
|
|
right_bound = root
|
|
|
|
for token in root.rights:
|
💫 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
|
|
|
if token.dep in np_right_deps:
|
|
|
|
left, right = noun_bounds(
|
|
|
|
doc, token, np_left_deps, np_right_deps, stop_deps
|
|
|
|
)
|
2020-07-22 23:18:46 +03:00
|
|
|
filter_func = lambda t: is_verb_token(t) or t.dep in stop_deps
|
|
|
|
if list(filter(filter_func, doc[left_bound.i : right.i],)):
|
2017-06-02 20:09:58 +03:00
|
|
|
break
|
|
|
|
else:
|
|
|
|
right_bound = right
|
|
|
|
return left_bound, right_bound
|
|
|
|
|
|
|
|
|
💫 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
|
|
|
SYNTAX_ITERATORS = {"noun_chunks": noun_chunks}
|