You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Underscore instead of hyphen for publish in Makefile.
* Increment version.
* Prefer shorter codepoint values when escaping for RE2.
* More uniformity in tests for regex expressions.
* Parameters actually accept string chars when iterating a character range.
* Add regex making function.
* Formatting change to bash commands in readme to make it easier to copy.
* Improve readability in a few docstring examples when rendered to markdown.
* Considering test parameterization.
- Added `to_nfc` test.
- Avoiding lru_cache when evalutating enum (just build expression on script initialization to prevent slowness for now).
- Additional/improved edge cases in some tests.
- Added reserved regex expressions to constants.
* Including requirements-test.txt for convenience.
* Use full match in test instead of search.
* Short-term implementation adding ability to change default regex flavor at any point.
* Update readme.
* RE2 should only be required for testing.
* Move `default_flavor` from `regex_toolkit.utils` to `regex_tookit.base` and add test for changing the default.
* Readme clean up.
To harness the toolkit's capabilities, you should import the necessary packages:
61
61
62
62
```python
63
63
import re
64
64
# and/or
65
65
import re2
66
+
import regex_toolkit as rtk
66
67
```
67
68
68
-
```python
69
-
import regex_toolkit
70
-
```
69
+
### Why Use `regex_toolkit`?
70
+
71
+
Regex definitions vary across languages and versions.
72
+
By using the toolkit, you can achieve a more consistent and comprehensive representation of unicode support.
73
+
It is especially useful to supplement base unicode sets with the latest definitions from other languages and standards.
74
+
75
+
### RE2 Overview
76
+
77
+
RE2 focuses on safely processing regular expressions, particularly from untrusted inputs.
78
+
It ensures both linear match time and efficient memory usage.
79
+
Although it might not always surpass other engines in speed, it intentionally omits features that depend solely on backtracking, like backreferences and look-around assertions.
80
+
81
+
A brief rundown of RE2 terminology:
82
+
83
+
-**BitState**: An execution engine that uses backtracking search.
84
+
-**bytecode**: The set of instructions that form an automaton.
85
+
-**DFA**: The engine for Deterministic Finite Automaton searches.
86
+
-**NFA**: Implements the Nondeterministic Finite Automaton search method.
87
+
-**OnePass**: A one-pass search execution engine.
88
+
-**pattern**: The textual form of a regex.
89
+
-**Prog**: The compiled version of a regex.
90
+
-**Regexp**: The parsed version of a regex.
91
+
-**Rune**: A character in terms of encoding, essentially a code point.
92
+
93
+
For an in-depth exploration, please refer to the [RE2 documentation](https://github.com/google/re2/wiki/Glossary).
To harness the toolkit's capabilities, you should import the necessary packages:
2
2
3
3
```python
4
4
import re
5
5
# and/or
6
6
import re2
7
+
import regex_toolkit as rtk
7
8
```
8
9
9
-
```python
10
-
import regex_toolkit
11
-
```
10
+
### Why Use `regex_toolkit`?
11
+
12
+
Regex definitions vary across languages and versions.
13
+
By using the toolkit, you can achieve a more consistent and comprehensive representation of unicode support.
14
+
It is especially useful to supplement base unicode sets with the latest definitions from other languages and standards.
15
+
16
+
### RE2 Overview
17
+
18
+
RE2 focuses on safely processing regular expressions, particularly from untrusted inputs.
19
+
It ensures both linear match time and efficient memory usage.
20
+
Although it might not always surpass other engines in speed, it intentionally omits features that depend solely on backtracking, like backreferences and look-around assertions.
21
+
22
+
A brief rundown of RE2 terminology:
23
+
24
+
- **BitState**: An execution engine that uses backtracking search.
25
+
- **bytecode**: The set of instructions that form an automaton.
26
+
- **DFA**: The engine for Deterministic Finite Automaton searches.
27
+
- **NFA**: Implements the Nondeterministic Finite Automaton search method.
28
+
- **OnePass**: A one-pass search execution engine.
29
+
- **pattern**: The textual form of a regex.
30
+
- **Prog**: The compiled version of a regex.
31
+
- **Regexp**: The parsed version of a regex.
32
+
- **Rune**: A character in terms of encoding, essentially a code point.
33
+
34
+
For an in-depth exploration, please refer to the [RE2 documentation](https://github.com/google/re2/wiki/Glossary).
0 commit comments