Minor tweaks

Author: uogbuji

AICONTEXT.md AICONTEXT-PYLIB.mdAICONTEXT.md renamed to AICONTEXT-PYLIB.md

@@ -1,4 +1,4 @@
-Additional context on this repository for AI tools & coding agents
+Additional context on this project for AI tools & coding agents
 
 - Python 3.12+ code, unless otherwise specified
 - Python code uses single outer quotes, including triple single quotes for e.g. docstrings
@@ -10,12 +10,13 @@ Additional context on this repository for AI tools & coding agents
 - Try to stick to 120 characters per line
   - if one of those comments would break this guideline, just put that comment above the line instead, as is standard convention
 - If there is a pyproject.toml in place, use it as a reference for builds, installs, etc. The basic packaging and dev preference, including if you have to supply your own pyproject.toml, is as follows:
-  - Use pyproject.toml with hatchling, not e.g. setup.py
+  - Prefer hatchling build system over setuptools, poetry, etc. Avoid setuptools as much as possible. No setup.py.
   - Reusable Python code modules are developed in the `pylib` folder, and installed using e.g. `uv pip install -U .`, which includes proper mapping to Python library package namespace via `tool.hatch.build.sources`. The `__init__.py` and other modules in the top-level package go directly in `pylib`, though submodules can use subdirectories, e.g. `pylib/a/b` becomes `installed_library_name.a.b`. Ultimately this will mean the installed package is importable as `from installed_library_name.etc import …`
-  - Yes this means editable and "dev mode" environments are NOT desirable, nor are shenanigans adding pylib to `sys.path`. Layer-efficient dockerization is an option if that's needed.
-  - The ethos is to always develop keeping things properly installable. No dev mode shortcuts
-  - Prefer hatchling build system over setuptools, poetry, etc. Avoid setuptools as much as possible. Use `[tool.hatch.build.sources]` to map source directories to package namespaces (e.g., `"pylib" = "installed_library_name"`).
   - Use `[tool.hatch.build.targets.wheel]` with `only-include = ["pylib"]` to ensure the pylib directory structure gets included properly in the wheel, avoiding the duplication issue that can occur with sources mapping
+  - Yes this means editable and "dev mode" environments are NOT desirable, nor are shenanigans adding pylib to `sys.path`. Layer-efficient dockerization is an option if that's needed.
+  - The ethos is to always develop keeping things properly installable. No dev mode shortcuts. Substantive modification to libray code requires e.g. `uv pip install -U .` each time.
+  - Note: This avoidance of editable installs can be relaxed for non-library code, such as demos or main app launch scripts (e.g. webapp back ends)
+  - If it's a CLI provided as part of a library, though, it should still use proper installation via `[project.scripts]` entry points (e.g., `ooriscout = 'ooriscout.cli.scout:main'`), which creates console scripts that work correctly after `uv pip install -U .`. The CLI module lives in `pylib/cli/` and exposes a `main()` function that uses fire to handle command-line arguments. 
 - **Debugging package issues**: When modules aren't importing correctly after installation, check:
   - That you are in the correct virtualenv (you may have to ask the developer)
   - Package structure in site-packages (e.g., `ls -la /path/to/site-packages/package_name/`)

demo/kgraph/README.md

@@ -45,9 +45,7 @@ Basic `.onya` format example:
 * occupation: Data Scientist
 ```
 
-Key elements:
-- **Document header**: Declares namespaces and base URI
-- **Nodes**: Marked with `# NodeName [Type]`
+There is a document header which declares namespaces and base IRIs (URIs). Node definitions are marked with `# NodeID [Type]`. The node ID is resolved against `@document` and the type against 
 - **Properties**: Listed with `* property: value`
 - **Types**: Entities can have one or more types
 
@@ -175,7 +173,7 @@ print(response.first_choice_text)
 ## Read-Only by Design
 
 `OnyaKB` is intentionally read-only:
-- **insert()** and **delete()** raise `NotImplementedError`
+- `insert()` and `delete()` raise `NotImplementedError`
 - Edit `.onya` files directly using your text editor
 - Reload by calling `cleanup()` then `setup()` again
 - This design encourages human curation and version control

pylib/config.py

@@ -19,6 +19,9 @@
 
 
 class attr_dict(dict):
+    '''
+    Dictionary with attribute access
+    '''
     # XXX: Should unknown attr access return None rather than raise?
     # If so, can just do: __getattr__ = dict.get
     # __getattr__ = dict.__getitem__

pylib/text/html.py

@@ -9,24 +9,20 @@
 import re
 import warnings
 
-# Just use tiktoken, even though it's OpenAI specific
-import tiktoken
-
 try:
     import cssutils  # pip install cssutils
 except ImportError:
     cssutils = None
     warnings.warn(
-        'Using html_helper without cssutils, which will limit features. May want to do e.g. `pip install cssutils`')
+        'Using html_helper without cssutils, which will limit features. Recommend e.g. `pip install cssutils`')
 
 # selectolax install is optional for OgbujiPT, but mandatory for html_helper
 try:
     from selectolax.parser import HTMLParser  # pip install selectolax
 except ImportError:
     HTMLParser = None
     warnings.warn(
-        'Cannot use html_helper without selectolax. May want to do e.g. `pip install selectolax`')
-
+        'Cannot use html_helper without selectolax. Recommend e.g. `pip install selectolax`')
 
 
 HTML_SAMPLE1 = '''\
@@ -124,6 +120,8 @@ def html_split(text: str, chunk_size: int, separator: str='\n\n', joiner=None, l
 
 
 def count_tokens(text: str) -> int:
+    # Just use tiktoken, even though it's OpenAI specific
+    import tiktoken
     encoder = tiktoken.encoding_for_model('gpt-3.5-turbo')
     tokens = encoder.encode(text)
     return len(tokens)

pyproject.toml

@@ -84,6 +84,10 @@ mega = [
   "docx2python",
   "PyPDF2",
   "PyCryptodome",
+  "tiktoken",
+  "cssutils",
+  "selectolax",
+  "fire",
   "qdrant-client",
   "streamlit",
   "watchdog",