From 9fa6f9fb403dd1d02526c0ee2ba1e1c1954d6e15 Mon Sep 17 00:00:00 2001 From: Jason Kessler Date: Mon, 16 Jan 2017 13:31:35 -0600 Subject: [PATCH] Origin of spacy.matcher attributes Make it clear that Matcher attributes live in spacy.matcher.attrs. --- website/docs/usage/rule-based-matching.jade | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/usage/rule-based-matching.jade b/website/docs/usage/rule-based-matching.jade index fde9ee4d7..7650e4a03 100644 --- a/website/docs/usage/rule-based-matching.jade +++ b/website/docs/usage/rule-based-matching.jade @@ -18,7 +18,9 @@ p Here's a minimal example. We first add a pattern that specifies three tokens: p | Once we've added the pattern, we can use the #[code matcher] as a - | callable, to receive a list of #[code (ent_id, start, end)] tuples: + | callable, to receive a list of #[code (ent_id, start, end)] tuples. + | Note that #[code LOWER] and #[code IS_PUNCT] are data attributes + | of #[code Matcher.attrs]. +code. from spacy.matcher import Matcher