parsely-dip 0.0.3__tar.gz → 0.0.4__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {parsely_dip-0.0.3/src/parsely_dip.egg-info → parsely_dip-0.0.4}/PKG-INFO +18 -12
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/README.md +17 -11
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/pyproject.toml +1 -1
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/__init__.py +1 -1
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/intents/day.py +13 -1
- {parsely_dip-0.0.3 → parsely_dip-0.0.4/src/parsely_dip.egg-info}/PKG-INFO +18 -12
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/LICENSE +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/setup.cfg +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/cli/__init__.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/cli/main.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/__init__.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/nlp.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/regex.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/registry.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/splitter.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/engine/stanza_service.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/intents/__init__.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/intents/scrum.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/intents/time.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/intents/weather.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip/patterns/__init__.py +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip.egg-info/SOURCES.txt +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip.egg-info/dependency_links.txt +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip.egg-info/entry_points.txt +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip.egg-info/requires.txt +0 -0
- {parsely_dip-0.0.3 → parsely_dip-0.0.4}/src/parsely_dip.egg-info/top_level.txt +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: parsely-dip
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.4
|
|
4
4
|
Summary: PARSELY-DIP: Deterministic Intent Parser — RegEx and NLP pipeline for intent recognition
|
|
5
5
|
Author-email: George Butiri <george@iseestudios.com>
|
|
6
6
|
License: Proprietary
|
|
@@ -455,40 +455,40 @@ The `tell_day` intent demonstrates the full power of the three-tier pipeline wit
|
|
|
455
455
|
Today is Sunday, March 29, 2026.
|
|
456
456
|
|
|
457
457
|
>>> what day will it be tomorrow
|
|
458
|
-
|
|
458
|
+
Tomorrow will be Monday, March 30, 2026.
|
|
459
459
|
|
|
460
460
|
>>> what day will it be in three days
|
|
461
|
-
in 3 days
|
|
461
|
+
in 3 days it will be Wednesday, April 01, 2026.
|
|
462
462
|
|
|
463
463
|
>>> what day is April Fools
|
|
464
|
-
April Fool's Day
|
|
464
|
+
April Fool's Day will be Wednesday, April 01, 2026.
|
|
465
465
|
|
|
466
466
|
>>> what day is on 4/1
|
|
467
|
-
4/1/2026
|
|
467
|
+
4/1/2026 will be Wednesday, April 01, 2026.
|
|
468
468
|
|
|
469
469
|
>>> when is easter
|
|
470
|
-
Easter
|
|
470
|
+
Easter will be Sunday, April 05, 2026.
|
|
471
471
|
|
|
472
472
|
>>> when is thanksgiving
|
|
473
|
-
Thanksgiving
|
|
473
|
+
Thanksgiving will be Thursday, November 26, 2026.
|
|
474
474
|
|
|
475
475
|
>>> when is the next 4th of July
|
|
476
|
-
Independence Day
|
|
476
|
+
Independence Day will be Saturday, July 04, 2026.
|
|
477
477
|
|
|
478
478
|
>>> when is mothers day
|
|
479
|
-
Mother's Day
|
|
479
|
+
Mother's Day will be Sunday, May 10, 2026.
|
|
480
480
|
|
|
481
481
|
>>> when is mlk day
|
|
482
482
|
Martin Luther King Jr. Day was Monday, January 19, 2026.
|
|
483
483
|
|
|
484
484
|
>>> what day is christmas
|
|
485
|
-
Christmas Day
|
|
485
|
+
Christmas Day will be Friday, December 25, 2026.
|
|
486
486
|
|
|
487
487
|
>>> what day is memorial day
|
|
488
|
-
Memorial Day
|
|
488
|
+
Memorial Day will be Monday, May 25, 2026.
|
|
489
489
|
|
|
490
490
|
>>> what day is labor day
|
|
491
|
-
Labor Day
|
|
491
|
+
Labor Day will be Monday, September 07, 2026.
|
|
492
492
|
```
|
|
493
493
|
|
|
494
494
|
### How It Works
|
|
@@ -869,6 +869,10 @@ Meanwhile, PARSELY-DIP's `tell_day` handler answers "what day will it be tomorro
|
|
|
869
869
|
|
|
870
870
|
An LLM answering "when is Easter" takes 1-3 seconds, costs tokens, and has a measurable chance of returning the wrong date. PARSELY-DIP answers in under 100ms, costs nothing, and the math is provably correct.
|
|
871
871
|
|
|
872
|
+
Later in the same session, the LLM assisting with development was asked to update completed task cards on the project board. It correctly marked the finished card as Done. Then, without being asked, it decided a second card "hadn't been worked on" and moved it out of the active column — overriding the developer's deliberate placement. A deterministic engine would have completed the matched action (update the finished card), noticed the remaining cards were outside the work scope, and asked what to do with them. The LLM assumed. The DI engine would have asked. That is the entire product thesis: deterministic systems execute what they match and stop. They do not extrapolate, infer, or helpfully override the user's intent.
|
|
873
|
+
|
|
874
|
+
These are not hypothetical examples. Both incidents happened in real time during the development of this package — the calendar math error while discussing the release date, and the card-moving incident during the session wrap-up. The tool that was being built to prevent exactly these kinds of errors was itself being developed by a system that kept making them.
|
|
875
|
+
|
|
872
876
|
### Domain-Specific Skill Files
|
|
873
877
|
|
|
874
878
|
The patterns loaded into PARSELY-DIP define the domain. The same engine serves completely different environments by swapping which `.patterns` and `_nlp.json` files are loaded.
|
|
@@ -927,6 +931,8 @@ Linguists and NLP researchers who understand constituency trees, dependency rela
|
|
|
927
931
|
|
|
928
932
|
## Status
|
|
929
933
|
|
|
934
|
+
v0.0.4 — Natural language tense in responses (future dates use "will be", past dates use "was"). "next" prefix word order fix. Additional "when will X be" query support.
|
|
935
|
+
|
|
930
936
|
v0.0.3 — Dynamic parameter passing from both regex and NLP layers to intent handlers via context dict. `tell_day` intent with full date resolution: relative dates (tomorrow, in 3 days), fixed holidays (Christmas, Halloween, Veterans Day), moving holidays with calculators (Easter computus, Thanksgiving, Memorial Day, Labor Day, MLK Day, Mother's Day, Father's Day, Columbus Day, Presidents Day), numeric dates (4/1), weekday names, ordinal patterns (4th of July), "next" prefix for future occurrence, and correct past/present/future tense in responses. `word2number` integration for written numerals ("three" to 3). `check_ability_time` ability-check intent that verifies the target handler works before responding. CLI reorganized: `parsely start`, `parsely --chat` (pipeline testing), `parsely --test` (structure explorer). Hot-reload patterns from disk on every query via mtime check (no restart needed). NLP pattern for modal verb + action verb + noun slot matching. Visual constituency tree display. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, domain-specific skill files, and hardware instantiation vision. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
931
937
|
|
|
932
938
|
v0.0.2 — Visual constituency tree display in interactive mode. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, and domain-specific skill file architecture. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
@@ -432,40 +432,40 @@ The `tell_day` intent demonstrates the full power of the three-tier pipeline wit
|
|
|
432
432
|
Today is Sunday, March 29, 2026.
|
|
433
433
|
|
|
434
434
|
>>> what day will it be tomorrow
|
|
435
|
-
|
|
435
|
+
Tomorrow will be Monday, March 30, 2026.
|
|
436
436
|
|
|
437
437
|
>>> what day will it be in three days
|
|
438
|
-
in 3 days
|
|
438
|
+
in 3 days it will be Wednesday, April 01, 2026.
|
|
439
439
|
|
|
440
440
|
>>> what day is April Fools
|
|
441
|
-
April Fool's Day
|
|
441
|
+
April Fool's Day will be Wednesday, April 01, 2026.
|
|
442
442
|
|
|
443
443
|
>>> what day is on 4/1
|
|
444
|
-
4/1/2026
|
|
444
|
+
4/1/2026 will be Wednesday, April 01, 2026.
|
|
445
445
|
|
|
446
446
|
>>> when is easter
|
|
447
|
-
Easter
|
|
447
|
+
Easter will be Sunday, April 05, 2026.
|
|
448
448
|
|
|
449
449
|
>>> when is thanksgiving
|
|
450
|
-
Thanksgiving
|
|
450
|
+
Thanksgiving will be Thursday, November 26, 2026.
|
|
451
451
|
|
|
452
452
|
>>> when is the next 4th of July
|
|
453
|
-
Independence Day
|
|
453
|
+
Independence Day will be Saturday, July 04, 2026.
|
|
454
454
|
|
|
455
455
|
>>> when is mothers day
|
|
456
|
-
Mother's Day
|
|
456
|
+
Mother's Day will be Sunday, May 10, 2026.
|
|
457
457
|
|
|
458
458
|
>>> when is mlk day
|
|
459
459
|
Martin Luther King Jr. Day was Monday, January 19, 2026.
|
|
460
460
|
|
|
461
461
|
>>> what day is christmas
|
|
462
|
-
Christmas Day
|
|
462
|
+
Christmas Day will be Friday, December 25, 2026.
|
|
463
463
|
|
|
464
464
|
>>> what day is memorial day
|
|
465
|
-
Memorial Day
|
|
465
|
+
Memorial Day will be Monday, May 25, 2026.
|
|
466
466
|
|
|
467
467
|
>>> what day is labor day
|
|
468
|
-
Labor Day
|
|
468
|
+
Labor Day will be Monday, September 07, 2026.
|
|
469
469
|
```
|
|
470
470
|
|
|
471
471
|
### How It Works
|
|
@@ -846,6 +846,10 @@ Meanwhile, PARSELY-DIP's `tell_day` handler answers "what day will it be tomorro
|
|
|
846
846
|
|
|
847
847
|
An LLM answering "when is Easter" takes 1-3 seconds, costs tokens, and has a measurable chance of returning the wrong date. PARSELY-DIP answers in under 100ms, costs nothing, and the math is provably correct.
|
|
848
848
|
|
|
849
|
+
Later in the same session, the LLM assisting with development was asked to update completed task cards on the project board. It correctly marked the finished card as Done. Then, without being asked, it decided a second card "hadn't been worked on" and moved it out of the active column — overriding the developer's deliberate placement. A deterministic engine would have completed the matched action (update the finished card), noticed the remaining cards were outside the work scope, and asked what to do with them. The LLM assumed. The DI engine would have asked. That is the entire product thesis: deterministic systems execute what they match and stop. They do not extrapolate, infer, or helpfully override the user's intent.
|
|
850
|
+
|
|
851
|
+
These are not hypothetical examples. Both incidents happened in real time during the development of this package — the calendar math error while discussing the release date, and the card-moving incident during the session wrap-up. The tool that was being built to prevent exactly these kinds of errors was itself being developed by a system that kept making them.
|
|
852
|
+
|
|
849
853
|
### Domain-Specific Skill Files
|
|
850
854
|
|
|
851
855
|
The patterns loaded into PARSELY-DIP define the domain. The same engine serves completely different environments by swapping which `.patterns` and `_nlp.json` files are loaded.
|
|
@@ -904,6 +908,8 @@ Linguists and NLP researchers who understand constituency trees, dependency rela
|
|
|
904
908
|
|
|
905
909
|
## Status
|
|
906
910
|
|
|
911
|
+
v0.0.4 — Natural language tense in responses (future dates use "will be", past dates use "was"). "next" prefix word order fix. Additional "when will X be" query support.
|
|
912
|
+
|
|
907
913
|
v0.0.3 — Dynamic parameter passing from both regex and NLP layers to intent handlers via context dict. `tell_day` intent with full date resolution: relative dates (tomorrow, in 3 days), fixed holidays (Christmas, Halloween, Veterans Day), moving holidays with calculators (Easter computus, Thanksgiving, Memorial Day, Labor Day, MLK Day, Mother's Day, Father's Day, Columbus Day, Presidents Day), numeric dates (4/1), weekday names, ordinal patterns (4th of July), "next" prefix for future occurrence, and correct past/present/future tense in responses. `word2number` integration for written numerals ("three" to 3). `check_ability_time` ability-check intent that verifies the target handler works before responding. CLI reorganized: `parsely start`, `parsely --chat` (pipeline testing), `parsely --test` (structure explorer). Hot-reload patterns from disk on every query via mtime check (no restart needed). NLP pattern for modal verb + action verb + noun slot matching. Visual constituency tree display. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, domain-specific skill files, and hardware instantiation vision. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
908
914
|
|
|
909
915
|
v0.0.2 — Visual constituency tree display in interactive mode. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, and domain-specific skill file architecture. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "parsely-dip"
|
|
7
|
-
version = "0.0.
|
|
7
|
+
version = "0.0.4"
|
|
8
8
|
description = "PARSELY-DIP: Deterministic Intent Parser — RegEx and NLP pipeline for intent recognition"
|
|
9
9
|
readme = "README.md"
|
|
10
10
|
license = {text = "Proprietary"}
|
|
@@ -289,12 +289,20 @@ def format_day_response(dt, description):
|
|
|
289
289
|
|
|
290
290
|
if description == "today":
|
|
291
291
|
return f"Today is {day_name}, {date_str}."
|
|
292
|
+
elif description == "yesterday":
|
|
293
|
+
return f"Yesterday was {day_name}, {date_str}."
|
|
294
|
+
elif description == "tomorrow":
|
|
295
|
+
return f"Tomorrow will be {day_name}, {date_str}."
|
|
296
|
+
elif description.startswith("in "):
|
|
297
|
+
if dt.date() < today:
|
|
298
|
+
return f"{description} it was {day_name}, {date_str}."
|
|
299
|
+
return f"{description} it will be {day_name}, {date_str}."
|
|
292
300
|
elif dt.date() < today:
|
|
293
301
|
return f"{description} was {day_name}, {date_str}."
|
|
294
302
|
elif dt.date() == today:
|
|
295
303
|
return f"{description} is today, {day_name}, {date_str}."
|
|
296
304
|
else:
|
|
297
|
-
return f"{description}
|
|
305
|
+
return f"{description} will be {day_name}, {date_str}."
|
|
298
306
|
|
|
299
307
|
|
|
300
308
|
def extract_date_reference(context):
|
|
@@ -334,6 +342,10 @@ def extract_date_reference(context):
|
|
|
334
342
|
ref_parts.append(text)
|
|
335
343
|
|
|
336
344
|
if ref_parts:
|
|
345
|
+
# Ensure "next" is at the front (Stanza parses it as ADJ modifier)
|
|
346
|
+
if 'next' in ref_parts and ref_parts[0] != 'next':
|
|
347
|
+
ref_parts.remove('next')
|
|
348
|
+
ref_parts.insert(0, 'next')
|
|
337
349
|
return ' '.join(ref_parts)
|
|
338
350
|
return None
|
|
339
351
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: parsely-dip
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.4
|
|
4
4
|
Summary: PARSELY-DIP: Deterministic Intent Parser — RegEx and NLP pipeline for intent recognition
|
|
5
5
|
Author-email: George Butiri <george@iseestudios.com>
|
|
6
6
|
License: Proprietary
|
|
@@ -455,40 +455,40 @@ The `tell_day` intent demonstrates the full power of the three-tier pipeline wit
|
|
|
455
455
|
Today is Sunday, March 29, 2026.
|
|
456
456
|
|
|
457
457
|
>>> what day will it be tomorrow
|
|
458
|
-
|
|
458
|
+
Tomorrow will be Monday, March 30, 2026.
|
|
459
459
|
|
|
460
460
|
>>> what day will it be in three days
|
|
461
|
-
in 3 days
|
|
461
|
+
in 3 days it will be Wednesday, April 01, 2026.
|
|
462
462
|
|
|
463
463
|
>>> what day is April Fools
|
|
464
|
-
April Fool's Day
|
|
464
|
+
April Fool's Day will be Wednesday, April 01, 2026.
|
|
465
465
|
|
|
466
466
|
>>> what day is on 4/1
|
|
467
|
-
4/1/2026
|
|
467
|
+
4/1/2026 will be Wednesday, April 01, 2026.
|
|
468
468
|
|
|
469
469
|
>>> when is easter
|
|
470
|
-
Easter
|
|
470
|
+
Easter will be Sunday, April 05, 2026.
|
|
471
471
|
|
|
472
472
|
>>> when is thanksgiving
|
|
473
|
-
Thanksgiving
|
|
473
|
+
Thanksgiving will be Thursday, November 26, 2026.
|
|
474
474
|
|
|
475
475
|
>>> when is the next 4th of July
|
|
476
|
-
Independence Day
|
|
476
|
+
Independence Day will be Saturday, July 04, 2026.
|
|
477
477
|
|
|
478
478
|
>>> when is mothers day
|
|
479
|
-
Mother's Day
|
|
479
|
+
Mother's Day will be Sunday, May 10, 2026.
|
|
480
480
|
|
|
481
481
|
>>> when is mlk day
|
|
482
482
|
Martin Luther King Jr. Day was Monday, January 19, 2026.
|
|
483
483
|
|
|
484
484
|
>>> what day is christmas
|
|
485
|
-
Christmas Day
|
|
485
|
+
Christmas Day will be Friday, December 25, 2026.
|
|
486
486
|
|
|
487
487
|
>>> what day is memorial day
|
|
488
|
-
Memorial Day
|
|
488
|
+
Memorial Day will be Monday, May 25, 2026.
|
|
489
489
|
|
|
490
490
|
>>> what day is labor day
|
|
491
|
-
Labor Day
|
|
491
|
+
Labor Day will be Monday, September 07, 2026.
|
|
492
492
|
```
|
|
493
493
|
|
|
494
494
|
### How It Works
|
|
@@ -869,6 +869,10 @@ Meanwhile, PARSELY-DIP's `tell_day` handler answers "what day will it be tomorro
|
|
|
869
869
|
|
|
870
870
|
An LLM answering "when is Easter" takes 1-3 seconds, costs tokens, and has a measurable chance of returning the wrong date. PARSELY-DIP answers in under 100ms, costs nothing, and the math is provably correct.
|
|
871
871
|
|
|
872
|
+
Later in the same session, the LLM assisting with development was asked to update completed task cards on the project board. It correctly marked the finished card as Done. Then, without being asked, it decided a second card "hadn't been worked on" and moved it out of the active column — overriding the developer's deliberate placement. A deterministic engine would have completed the matched action (update the finished card), noticed the remaining cards were outside the work scope, and asked what to do with them. The LLM assumed. The DI engine would have asked. That is the entire product thesis: deterministic systems execute what they match and stop. They do not extrapolate, infer, or helpfully override the user's intent.
|
|
873
|
+
|
|
874
|
+
These are not hypothetical examples. Both incidents happened in real time during the development of this package — the calendar math error while discussing the release date, and the card-moving incident during the session wrap-up. The tool that was being built to prevent exactly these kinds of errors was itself being developed by a system that kept making them.
|
|
875
|
+
|
|
872
876
|
### Domain-Specific Skill Files
|
|
873
877
|
|
|
874
878
|
The patterns loaded into PARSELY-DIP define the domain. The same engine serves completely different environments by swapping which `.patterns` and `_nlp.json` files are loaded.
|
|
@@ -927,6 +931,8 @@ Linguists and NLP researchers who understand constituency trees, dependency rela
|
|
|
927
931
|
|
|
928
932
|
## Status
|
|
929
933
|
|
|
934
|
+
v0.0.4 — Natural language tense in responses (future dates use "will be", past dates use "was"). "next" prefix word order fix. Additional "when will X be" query support.
|
|
935
|
+
|
|
930
936
|
v0.0.3 — Dynamic parameter passing from both regex and NLP layers to intent handlers via context dict. `tell_day` intent with full date resolution: relative dates (tomorrow, in 3 days), fixed holidays (Christmas, Halloween, Veterans Day), moving holidays with calculators (Easter computus, Thanksgiving, Memorial Day, Labor Day, MLK Day, Mother's Day, Father's Day, Columbus Day, Presidents Day), numeric dates (4/1), weekday names, ordinal patterns (4th of July), "next" prefix for future occurrence, and correct past/present/future tense in responses. `word2number` integration for written numerals ("three" to 3). `check_ability_time` ability-check intent that verifies the target handler works before responding. CLI reorganized: `parsely start`, `parsely --chat` (pipeline testing), `parsely --test` (structure explorer). Hot-reload patterns from disk on every query via mtime check (no restart needed). NLP pattern for modal verb + action verb + noun slot matching. Visual constituency tree display. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, domain-specific skill files, and hardware instantiation vision. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
931
937
|
|
|
932
938
|
v0.0.2 — Visual constituency tree display in interactive mode. Expanded documentation with NLP vs RegEx tradeoff analysis, parse tree examples, slot-based matching, and domain-specific skill file architecture. Proprietary license aligned with python-tapestry. GitHub repository live.
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|