search-parser 0.0.2__tar.gz → 0.4.0__tar.gz

{search_parser-0.0.2 → search_parser-0.4.0}/.github/pull_request_template.md

@@ -15,7 +15,7 @@ Brief description of the changes.
 - [ ] I have added tests that prove my fix/feature works
 - [ ] All new and existing tests pass (`uv run pytest`)
 - [ ] Linting passes (`uv run ruff check .`)
-- [ ] Type checking passes (`uv run mypy src/search_engine_parser`)
+- [ ] Type checking passes (`uv run mypy src/search_parser`)
 - [ ] I have updated documentation as needed
 
 ## Test Plan

{search_parser-0.0.2 → search_parser-0.4.0}/.github/workflows/codeql.yml

@@ -57,7 +57,7 @@ jobs:
         # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v4
+      uses: actions/checkout@v6
 
     # Add any setup steps before running the `github/codeql-action/init` action.
     # This includes steps like installing compilers or runtimes (`actions/setup-node`

{search_parser-0.0.2 → search_parser-0.4.0}/.github/workflows/coverage-badge.yml

@@ -23,7 +23,7 @@ jobs:
 
       - name: Run tests with coverage
         run: |
-          uv run pytest --cov=search_engine_parser --cov-report=term --cov-report=json
+          uv run pytest --cov=search_parser --cov-report=term --cov-report=json
           COVERAGE=$(python -c "import json; print(int(float(json.load(open('coverage.json'))['totals']['percent_covered_display'])))")
           echo "COVERAGE=${COVERAGE}%" >> $GITHUB_ENV
           if [ "$COVERAGE" -ge 90 ]; then echo "COVERAGE_COLOR=brightgreen" >> $GITHUB_ENV;

{search_parser-0.0.2 → search_parser-0.4.0}/.github/workflows/lint.yml

@@ -30,4 +30,4 @@ jobs:
         run: uv run ruff format --check .
 
       - name: Run mypy
-        run: uv run mypy src/search_engine_parser
+        run: uv run mypy src/search_parser

{search_parser-0.0.2 → search_parser-0.4.0}/.github/workflows/publish.yml

@@ -3,6 +3,7 @@ name: Publish to PyPI
 on:
   release:
     types: [published]
+  workflow_dispatch:
 
 jobs:
   deploy:

{search_parser-0.0.2 → search_parser-0.4.0}/.github/workflows/test.yml

@@ -30,7 +30,7 @@ jobs:
         run: uv sync --all-extras
 
       - name: Run tests with coverage
-        run: uv run pytest --cov=search_engine_parser --cov-report=xml --cov-report=term --cov-report=html
+        run: uv run pytest --cov=search_parser --cov-report=xml --cov-report=term --cov-report=html
 
       - name: Upload coverage to Codecov
         uses: codecov/codecov-action@v5
@@ -41,7 +41,7 @@ jobs:
           token: ${{ secrets.CODECOV_TOKEN }}
 
       - name: Upload coverage HTML artifact
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: matrix.python-version == '3.11'
         with:
           name: coverage-report

{search_parser-0.0.2 → search_parser-0.4.0}/.gitignore

@@ -48,4 +48,5 @@ Thumbs.db
 
 # uv
 
-search_parser_prompt.md
+search_parser_prompt.md
+

{search_parser-0.0.2 → search_parser-0.4.0}/CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+---
+
+## [0.4.0] - 2026-03-05
+
+### Added
+
+- **Google parser: Jobs** — new `jobs` field on `SearchResults` containing job listings from the Google Jobs widget. Each entry has `result_type="job"` with `metadata["company"]` and `metadata["location"]` fields. Jobs are never included in the organic `results` list.
+- **Google parser: Discussions and forums** — new `discussions` field on `SearchResults` containing entries from the "Discussions and forums" widget. Each entry has `result_type="discussion"` with a `description` excerpt and `metadata["source"]` (platform, forum, comment count, and date).
+- New `result_type` values `"job"` and `"discussion"` added to the `SearchResult` model's Literal type.
+- Markdown formatter now renders `## Jobs` and `## Discussions and Forums` sections when those fields are present.
+- Unit tests for jobs and discussions parsing using the `supply-chain-director-jobs.html` fixture.
+
+---
+
+## [0.3.0] - 2026-02-21
+
+### Changed
+
+- Renamed all stale `search_engine_parser` references to `search_parser` across config, docs, and CI workflows.
+- Fixed `pyproject.toml`: CLI entry point, hatch build target, and mypy `files` path all now point to `src/search_parser`.
+- Synced `__version__.py` to match `pyproject.toml`.
+- Added author and publisher metadata (`linksc`, `hello@link.sc`) to `pyproject.toml`.
+- Updated package description with explicit search engine names and output formats for better discoverability.
+
+---
+
+## [0.2.0] - 2026-02-20
+
 ### Added
 
 - `SearchResults.to_json(indent=2)` — serialize results directly to a JSON string without going through `SearchParser`.
@@ -29,6 +57,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `SearchResults.people_also_search: list[SearchResult]` — related search items (new)
   - `SearchResults.related_products: list[SearchResult]` — product ad suggestions (new)
 
+### Fixed
+
+- **Security:** `SearchEngineDetector._check_url_patterns` replaced substring `in href` checks with `urlparse` hostname parsing against an explicit allowlist (`_ALLOWED_HOSTS`), preventing false positives from URLs like `http://evil.com/google.com`.
+- **Security:** `DuckDuckGoParser.can_parse` replaced `"duckduckgo.com" in href` substring check with `urlparse` hostname comparison (exact match or `.duckduckgo.com` subdomain).
+- **CI:** Added explicit `permissions: contents: read` blocks to `test.yml`, `lint.yml`, and `coverage-badge.yml` workflows to follow least-privilege GITHUB_TOKEN scoping.
+
 ### Migration
 
 If you were filtering `results.results` by `result_type`, update your code:
@@ -62,5 +96,8 @@ sponsored = results.sponsored         # list[SearchResult]
 - CI/CD workflows for testing, linting, coverage, and publishing.
 - Pre-commit hooks for ruff and mypy.
 
-[Unreleased]: https://github.com/getlinksc/search-parser/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/getlinksc/search-parser/compare/v0.4.0...HEAD
+[0.4.0]: https://github.com/getlinksc/search-parser/compare/v0.3.0...v0.4.0
+[0.3.0]: https://github.com/getlinksc/search-parser/compare/v0.2.0...v0.3.0
+[0.2.0]: https://github.com/getlinksc/search-parser/compare/v0.1.0...v0.2.0
 [0.1.0]: https://github.com/getlinksc/search-parser/releases/tag/v0.1.0

{search_parser-0.0.2 → search_parser-0.4.0}/CLAUDE.md

@@ -15,16 +15,16 @@ Using `uv` for fast, modern Python package management.
 ```bash
 uv sync --all-extras          # Install/sync all dependencies
 uv run pytest                 # Run tests
-uv run pytest --cov=search_engine_parser --cov-report=term  # Tests with coverage
+uv run pytest --cov=search_parser --cov-report=term  # Tests with coverage
 uv run ruff check .           # Lint code
 uv run ruff format .          # Format code
-uv run mypy src/search_engine_parser  # Type check
+uv run mypy src/search_parser  # Type check
 ```
 
 ## Adding a New Search Engine Parser
-1. Create `src/search_engine_parser/parsers/engine_name.py`
+1. Create `src/search_parser/parsers/engine_name.py`
 2. Implement class extending `BaseParser` with `engine_name`, `parse()`, and `can_parse()` methods
-3. Register in `src/search_engine_parser/parsers/__init__.py`
+3. Register in `src/search_parser/parsers/__init__.py`
 4. Add HTML test fixtures in `tests/fixtures/engine_name/`
 5. Write unit tests in `tests/unit/test_engine_name_parser.py`
 

{search_parser-0.0.2 → search_parser-0.4.0}/CONTRIBUTING.md

@@ -45,7 +45,7 @@ Adding support for a new search engine is straightforward. Follow these steps:
 
 ### Step 1: Create the parser module
 
-Create a new file at `src/search_engine_parser/engines/<engine_name>.py`:
+Create a new file at `src/search_parser/parsers/<engine_name>.py`:
 
 ```python
 """Parser for <EngineName> search results."""
@@ -56,7 +56,7 @@ from typing import Any
 
 from bs4 import BeautifulSoup, Tag
 
-from search_engine_parser.engines.base import BaseParser, SearchResult
+from search_parser.engines.base import BaseParser, SearchResult
 
 
 class EnginNameParser(BaseParser):
@@ -84,10 +84,10 @@ class EnginNameParser(BaseParser):
 
 ### Step 2: Register the parser
 
-Add your parser to the engine registry in `src/search_engine_parser/engines/__init__.py`:
+Add your parser to the engine registry in `src/search_parser/parsers/__init__.py`:
 
 ```python
-from search_engine_parser.engines.engine_name import EngineNameParser
+from search_parser.engines.engine_name import EngineNameParser
 
 ENGINES: list[type[BaseParser]] = [
     GoogleParser,
@@ -118,7 +118,7 @@ Create `tests/engines/test_<engine_name>.py`:
 import json
 from pathlib import Path
 
-from search_engine_parser.engines.engine_name import EngineNameParser
+from search_parser.engines.engine_name import EngineNameParser
 
 FIXTURES = Path(__file__).parent.parent / "fixtures" / "<engine_name>"
 
@@ -176,7 +176,7 @@ Key style rules:
 uv run pytest
 
 # Run with coverage
-uv run pytest --cov=search_engine_parser --cov-report=term-missing
+uv run pytest --cov=search_parser --cov-report=term-missing
 
 # Run a specific test file
 uv run pytest tests/engines/test_google.py

{search_parser-0.0.2 → search_parser-0.4.0}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: search-parser
-Version: 0.0.2
-Summary: Parse search engine HTML results into structured data
+Version: 0.4.0
+Summary: Parse Google, Bing, and DuckDuckGo HTML search results into JSON, Markdown, or dict — with auto-detection
 Project-URL: Homepage, https://github.com/getlinksc/search-parser
 Project-URL: Documentation, https://getlinksc.github.io/search-parser
 Project-URL: Repository, https://github.com/getlinksc/search-parser
 Project-URL: Issues, https://github.com/getlinksc/search-parser/issues
 Project-URL: Changelog, https://github.com/getlinksc/search-parser/blob/main/CHANGELOG.md
-Author-email: Your Name <you@example.com>
+Author-email: linksc <hello@link.sc>
 License: Apache-2.0
 License-File: LICENSE
 Keywords: bing,duckduckgo,google,parser,scraping,search
@@ -51,7 +51,7 @@ Description-Content-Type: text/markdown
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 [![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
-**Parse search engine HTML results into structured data (JSON, Markdown) with auto-detection.**
+**Parse Google, Bing, and DuckDuckGo HTML search results into JSON, Markdown, or Python dict — with automatic search engine detection.**
 
 `search-parser` takes raw HTML from Google, Bing, and DuckDuckGo and extracts every result type — organic results, featured snippets, AI Overviews, People Also Ask, sponsored ads, and more — into clean, typed Python objects. It auto-detects the search engine from the HTML, so you never have to specify which parser to use.
 
@@ -60,7 +60,7 @@ Description-Content-Type: text/markdown
 ## Quick Start
 
 ```python
-from search_engine_parser import SearchParser
+from search_parser import SearchParser
 
 parser = SearchParser()
 html = open("google_results.html").read()
@@ -120,6 +120,8 @@ pip install search-parser
 | What People Are Saying | `people_saying` | ✓ | — | — |
 | People Also Search For | `people_also_search` | ✓ | — | — |
 | Related Products & Services | `related_products` | ✓ | — | — |
+| Jobs | `jobs` | ✓ | — | — |
+| Discussions and forums | `discussions` | ✓ | — | — |
 
 ---
 
@@ -161,6 +163,15 @@ for ad in data["sponsored"]:
 for product in data["related_products"]:
     print(product["title"])
 
+# Jobs (title, metadata["company"], metadata["location"])
+for job in data["jobs"]:
+    print(job["title"], job["metadata"]["company"], job["metadata"]["location"])
+
+# Discussions (title, url, description, metadata["source"])
+for disc in data["discussions"]:
+    print(disc["title"], disc["url"])
+    print(disc["metadata"]["source"])
+
 # Metadata
 print(data["search_engine"])        # "google"
 print(data["query"])                # "python web scraping"
@@ -173,7 +184,7 @@ print(data["detection_confidence"]) # 0.95
 When you need the typed `SearchResults` object instead of a dict, call the engine parser directly. The model exposes `to_json()` and `to_markdown()` convenience methods:
 
 ```python
-from search_engine_parser.parsers.google import GoogleParser
+from search_parser.parsers.google import GoogleParser
 
 parser = GoogleParser()
 results = parser.parse(html)  # returns SearchResults
@@ -181,7 +192,7 @@ results = parser.parse(html)  # returns SearchResults
 # Typed access — no dict key lookups
 print(results.query)
 print(results.total_results)
-print(len(results.results))          # organic count
+print(len(results.results))  # organic count
 
 if results.featured_snippet:
     print(results.featured_snippet.title)
@@ -197,9 +208,9 @@ for post in results.people_saying:
     print(post.title, post.url)
 
 # Convert to JSON or Markdown directly on the model
-json_str  = results.to_json()
-json_str  = results.to_json(indent=4)  # custom indent
-md_str    = results.to_markdown()
+json_str = results.to_json()
+json_str = results.to_json(indent=4)  # custom indent
+md_str = results.to_markdown()
 ```
 
 ---
@@ -244,6 +255,31 @@ md_str    = results.to_markdown()
   "people_saying": [],
   "people_also_search": [],
   "related_products": [],
+  "jobs": [
+    {
+      "title": "Global Supply Chain Director",
+      "url": "https://www.google.com/search?q=%22Supply+Chain+Director&udm=8",
+      "description": null,
+      "position": 0,
+      "result_type": "job",
+      "metadata": {
+        "company": "InterSources, Inc.",
+        "location": "San Jose, CA  •  via Ladders"
+      }
+    }
+  ],
+  "discussions": [
+    {
+      "title": "Being considered for Director of Supply Chain",
+      "url": "https://www.reddit.com/r/supplychain/comments/1ib0c1a/being_considered_for_director_of_supply_chain/",
+      "description": "I work for a mid-sized company as a Procurement Manager...",
+      "position": 0,
+      "result_type": "discussion",
+      "metadata": {
+        "source": "Reddit · r/supplychain · 10+ comments · 1 year ago"
+      }
+    }
+  ],
   "detection_confidence": 0.95,
   "parsed_at": "2026-02-21T00:00:00Z",
   "metadata": {}
@@ -276,6 +312,26 @@ Web scraping is the process of extracting data from websites...
 Learn how to scrape websites with Python...
 
 **URL:** https://realpython.com/python-web-scraping/
+
+---
+
+## Jobs
+
+### Global Supply Chain Director
+
+**Company:** InterSources, Inc.
+**Location:** San Jose, CA  •  via Ladders
+**URL:** https://www.google.com/search?q=%22Supply+Chain+Director&udm=8
+
+---
+
+## Discussions and Forums
+
+### Being considered for Director of Supply Chain
+
+I work for a mid-sized company as a Procurement Manager...
+
+**URL:** https://www.reddit.com/r/supplychain/comments/1ib0c1a/being_considered_for_director_of_supply_chain/
 ```
 
 ---

{search_parser-0.0.2 → search_parser-0.4.0}/README.md

@@ -8,7 +8,7 @@
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 [![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
-**Parse search engine HTML results into structured data (JSON, Markdown) with auto-detection.**
+**Parse Google, Bing, and DuckDuckGo HTML search results into JSON, Markdown, or Python dict — with automatic search engine detection.**
 
 `search-parser` takes raw HTML from Google, Bing, and DuckDuckGo and extracts every result type — organic results, featured snippets, AI Overviews, People Also Ask, sponsored ads, and more — into clean, typed Python objects. It auto-detects the search engine from the HTML, so you never have to specify which parser to use.
 
@@ -17,7 +17,7 @@
 ## Quick Start
 
 ```python
-from search_engine_parser import SearchParser
+from search_parser import SearchParser
 
 parser = SearchParser()
 html = open("google_results.html").read()
@@ -77,6 +77,8 @@ pip install search-parser
 | What People Are Saying | `people_saying` | ✓ | — | — |
 | People Also Search For | `people_also_search` | ✓ | — | — |
 | Related Products & Services | `related_products` | ✓ | — | — |
+| Jobs | `jobs` | ✓ | — | — |
+| Discussions and forums | `discussions` | ✓ | — | — |
 
 ---
 
@@ -118,6 +120,15 @@ for ad in data["sponsored"]:
 for product in data["related_products"]:
     print(product["title"])
 
+# Jobs (title, metadata["company"], metadata["location"])
+for job in data["jobs"]:
+    print(job["title"], job["metadata"]["company"], job["metadata"]["location"])
+
+# Discussions (title, url, description, metadata["source"])
+for disc in data["discussions"]:
+    print(disc["title"], disc["url"])
+    print(disc["metadata"]["source"])
+
 # Metadata
 print(data["search_engine"])        # "google"
 print(data["query"])                # "python web scraping"
@@ -130,7 +141,7 @@ print(data["detection_confidence"]) # 0.95
 When you need the typed `SearchResults` object instead of a dict, call the engine parser directly. The model exposes `to_json()` and `to_markdown()` convenience methods:
 
 ```python
-from search_engine_parser.parsers.google import GoogleParser
+from search_parser.parsers.google import GoogleParser
 
 parser = GoogleParser()
 results = parser.parse(html)  # returns SearchResults
@@ -138,7 +149,7 @@ results = parser.parse(html)  # returns SearchResults
 # Typed access — no dict key lookups
 print(results.query)
 print(results.total_results)
-print(len(results.results))          # organic count
+print(len(results.results))  # organic count
 
 if results.featured_snippet:
     print(results.featured_snippet.title)
@@ -154,9 +165,9 @@ for post in results.people_saying:
     print(post.title, post.url)
 
 # Convert to JSON or Markdown directly on the model
-json_str  = results.to_json()
-json_str  = results.to_json(indent=4)  # custom indent
-md_str    = results.to_markdown()
+json_str = results.to_json()
+json_str = results.to_json(indent=4)  # custom indent
+md_str = results.to_markdown()
 ```
 
 ---
@@ -201,6 +212,31 @@ md_str    = results.to_markdown()
   "people_saying": [],
   "people_also_search": [],
   "related_products": [],
+  "jobs": [
+    {
+      "title": "Global Supply Chain Director",
+      "url": "https://www.google.com/search?q=%22Supply+Chain+Director&udm=8",
+      "description": null,
+      "position": 0,
+      "result_type": "job",
+      "metadata": {
+        "company": "InterSources, Inc.",
+        "location": "San Jose, CA  •  via Ladders"
+      }
+    }
+  ],
+  "discussions": [
+    {
+      "title": "Being considered for Director of Supply Chain",
+      "url": "https://www.reddit.com/r/supplychain/comments/1ib0c1a/being_considered_for_director_of_supply_chain/",
+      "description": "I work for a mid-sized company as a Procurement Manager...",
+      "position": 0,
+      "result_type": "discussion",
+      "metadata": {
+        "source": "Reddit · r/supplychain · 10+ comments · 1 year ago"
+      }
+    }
+  ],
   "detection_confidence": 0.95,
   "parsed_at": "2026-02-21T00:00:00Z",
   "metadata": {}
@@ -233,6 +269,26 @@ Web scraping is the process of extracting data from websites...
 Learn how to scrape websites with Python...
 
 **URL:** https://realpython.com/python-web-scraping/
+
+---
+
+## Jobs
+
+### Global Supply Chain Director
+
+**Company:** InterSources, Inc.
+**Location:** San Jose, CA  •  via Ladders
+**URL:** https://www.google.com/search?q=%22Supply+Chain+Director&udm=8
+
+---
+
+## Discussions and Forums
+
+### Being considered for Director of Supply Chain
+
+I work for a mid-sized company as a Procurement Manager...
+
+**URL:** https://www.reddit.com/r/supplychain/comments/1ib0c1a/being_considered_for_director_of_supply_chain/
 ```
 
 ---

{search_parser-0.0.2 → search_parser-0.4.0}/docs/adding_search_engine.md

@@ -4,16 +4,16 @@ This guide walks you through adding support for a new search engine.
 
 ## Step 1: Create the Parser
 
-Create `src/search_engine_parser/parsers/myengine.py`:
+Create `src/search_parser/parsers/myengine.py`:
 
 ```python
 from __future__ import annotations
 
 from bs4 import BeautifulSoup, Tag
 
-from search_engine_parser.core.models import SearchResult, SearchResults
-from search_engine_parser.parsers.base import BaseParser
-from search_engine_parser.utils import clean_text, make_soup
+from search_parser.core.models import SearchResult, SearchResults
+from search_parser.parsers.base import BaseParser
+from search_parser.utils import clean_text, make_soup
 
 
 class MyEngineParser(BaseParser):
@@ -58,14 +58,14 @@ class MyEngineParser(BaseParser):
 
 - `results` must contain **organic results only**. Sponsored ads go in `sponsored`, featured snippets in `featured_snippet`, etc.
 - Return an empty `SearchResults` (with `results=[]`) on malformed HTML — never raise.
-- Use `clean_text()` from `search_engine_parser.utils` to normalize whitespace.
+- Use `clean_text()` from `search_parser.utils` to normalize whitespace.
 
 ## Step 2: Register the Parser
 
-Add to `src/search_engine_parser/parsers/__init__.py`:
+Add to `src/search_parser/parsers/__init__.py`:
 
 ```python
-from search_engine_parser.parsers.myengine import MyEngineParser
+from search_parser.parsers.myengine import MyEngineParser
 
 PARSER_REGISTRY: dict[str, type[BaseParser]] = {
     "google": GoogleParser,
@@ -105,5 +105,5 @@ Run the full test suite and linting before submitting:
 ```bash
 uv run pytest
 uv run ruff check .
-uv run mypy src/search_engine_parser
+uv run mypy src/search_parser
 ```

{search_parser-0.0.2 → search_parser-0.4.0}/docs/api_reference.md

@@ -2,7 +2,7 @@
 
 ## SearchParser
 
-::: search_engine_parser.SearchParser
+::: search_parser.SearchParser
     options:
       show_root_heading: true
       members:
@@ -10,28 +10,28 @@
 
 ## Models
 
-::: search_engine_parser.core.models.SearchResult
+::: search_parser.core.models.SearchResult
     options:
       show_root_heading: true
 
-::: search_engine_parser.core.models.SearchResults
+::: search_parser.core.models.SearchResults
     options:
       show_root_heading: true
 
 ## Parsers
 
-::: search_engine_parser.parsers.base.BaseParser
+::: search_parser.parsers.base.BaseParser
     options:
       show_root_heading: true
 
 ## Formatters
 
-::: search_engine_parser.formatters.base.BaseFormatter
+::: search_parser.formatters.base.BaseFormatter
     options:
       show_root_heading: true
 
 ## Exceptions
 
-::: search_engine_parser.exceptions
+::: search_parser.exceptions
     options:
       show_root_heading: true

{search_parser-0.0.2 → search_parser-0.4.0}/docs/examples/advanced_usage.md

@@ -5,7 +5,7 @@
 ```python
 import json
 from pathlib import Path
-from search_engine_parser import SearchParser
+from search_parser import SearchParser
 
 parser = SearchParser()
 
@@ -22,8 +22,8 @@ for html_file in Path("html_files").glob("*.html"):
 ```python
 import csv
 import io
-from search_engine_parser.core.models import SearchResults
-from search_engine_parser.formatters.base import BaseFormatter
+from search_parser.core.models import SearchResults
+from search_parser.formatters.base import BaseFormatter
 
 
 class CSVFormatter(BaseFormatter):
@@ -39,7 +39,7 @@ class CSVFormatter(BaseFormatter):
 Use it with the engine parser directly (which returns a `SearchResults` object):
 
 ```python
-from search_engine_parser.parsers.google import GoogleParser
+from search_parser.parsers.google import GoogleParser
 
 results = GoogleParser().parse(html)
 csv_output = CSVFormatter().format(results)
@@ -50,7 +50,7 @@ csv_output = CSVFormatter().format(results)
 Each result type has its own field on `SearchResults` — no filtering by `result_type` needed:
 
 ```python
-from search_engine_parser.parsers.google import GoogleParser
+from search_parser.parsers.google import GoogleParser
 
 results = GoogleParser().parse(html)
 
@@ -110,8 +110,8 @@ prompt = f"Summarize these search results:\n\n{results.to_markdown()}"
 ## Error Handling
 
 ```python
-from search_engine_parser import SearchParser
-from search_engine_parser.exceptions import (
+from search_parser import SearchParser
+from search_parser.exceptions import (
     SearchEngineDetectionError,
     ParserNotFoundError,
     ParseError,

{search_parser-0.0.2 → search_parser-0.4.0}/docs/examples/basic_usage.md

@@ -3,7 +3,7 @@
 ## Parsing Search Results
 
 ```python
-from search_engine_parser import SearchParser
+from search_parser import SearchParser
 
 parser = SearchParser()
 
@@ -30,13 +30,13 @@ When you use an engine parser directly, the returned `SearchResults` object has
 `to_json()` and `to_markdown()` methods:
 
 ```python
-from search_engine_parser.parsers.google import GoogleParser
+from search_parser.parsers.google import GoogleParser
 
 results = GoogleParser().parse(html)
 
-json_str = results.to_json()          # same as JSONFormatter().format(results)
+json_str = results.to_json()  # same as JSONFormatter().format(results)
 json_str = results.to_json(indent=4)  # custom indentation
-md_str   = results.to_markdown()      # same as MarkdownFormatter().format(results)
+md_str = results.to_markdown()  # same as MarkdownFormatter().format(results)
 ```
 
 ## Accessing Result Types