open-news-api 0.1.1__tar.gz

open_news_api-0.1.1/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- *(Nothing yet – this section tracks upcoming features for the next release)*
+
+---
+
+## [0.1.1] - 2026-06-18
+
+### Fixed
+- Packaging metadata for PyPI release (no functional changes).
+
+*The package name may vary due to some PyPI issue, so it is recomended to use correct package name provided in README*
+
+---
+
+## [0.1.0] - 2026-06-17
+
+### Added
+- **Core Article Extraction**: Fetch and parse full-text articles from any news URL using a custom built pipeline.
+- **Live News Feeds**: Access real-time headlines from 10+ countries and multiple categories (business, tech, sports, etc.).
+- **Google News Search**: Search for specific topics and automatically decode obfuscated Google News URLs to get clean article links.
+- **RSS Discovery & Fetching**: Automatically discover RSS/Atom feeds from a website URL and fetch full feed entries.
+- **Batch Processing**: Process multiple URLs or feeds in bulk with efficient concurrency.
+- **Simple Summarization**: Generate concise summaries of articles (supports multiple backends).
+- **Smart Caching**: Built-in caching mechanism to reduce API calls and speed up repeated requests.
+- **Python 3.8+ Support**: Compatible with Python 3.8, 3.9, 3.10, 3.11, and 3.12.
+
+---
+
+## [Unreleased] - Future Plans
+
+- **No Plans Yet**: Please help / suggest features that could be plugged here.
+
+---
+
+[0.1.1]: https://github.com/alphap365/open-news/releases/tag/v0.1.1

open_news_api-0.1.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[alphap365@example.com](mailto:alphap365@example.com) (replace with your actual email address).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

open_news_api-0.1.1/CONTRIBUTING.md

@@ -0,0 +1,108 @@
+# Contributing to Open News
+
+Thank you for your interest in contributing to `open-news`! This document outlines the process for reporting issues, suggesting improvements, and submitting code changes.
+
+## Table of Contents
+- [Code of Conduct](#code-of-conduct)
+- [How to Report Issues](#how-to-report-issues)
+- [Suggesting Enhancements](#suggesting-enhancements)
+- [Development Setup](#development-setup)
+- [Coding Standards](#coding-standards)
+- [Testing](#testing)
+- [Submitting Pull Requests](#submitting-pull-requests)
+- [Questions?](#questions)
+
+## Code of Conduct
+We expect all contributors to be respectful and constructive. Harassment, hate speech, or any form of abuse will not be tolerated.
+
+## How to Report Issues
+If you find a bug, please open a GitHub issue with the following:
+
+- **Clear title** describing the problem.
+- **Steps to reproduce** (include URLs, code snippets, and the exact command you ran).
+- **Expected vs. actual behaviour**.
+- **Environment** (Python version, OS, package versions from `pip list`).
+- **Logs** (if any, with `DEBUG` logging enabled).
+
+## Suggesting Enhancements
+We welcome ideas for new features or improvements. Before opening an issue, search existing issues to avoid duplicates.
+
+In your suggestion, explain:
+- What problem it solves.
+- How you envision the API or behaviour.
+- Any alternatives you’ve considered.
+
+## Development Setup
+1. **Fork the repository** and clone it locally.
+2. **Set up a virtual environment** (recommended):
+   ```bash
+   python -m venv venv
+   source venv/bin/activate      # Linux/macOS
+   venv\Scripts\activate         # Windows
+   ```
+3. **Install the package in editable mode with development dependencies**:
+   ```bash
+   pip install -e .[dev]
+   ```
+   The `[dev]` extra should include `pytest`, `mypy`, `black`, `ruff`, etc. (See example `pyproject.toml` below.)
+4. **Install NLTK data** (used by `newspaper4k`):
+   ```bash
+   python -m nltk.downloader punkt
+   ```
+
+## Coding Standards
+- **Formatting**: Use [Black](https://black.readthedocs.io/) with the default settings.
+- **Linting**: Use [Ruff](https://docs.astral.sh/ruff/) (or `flake8` + `pylint`).
+- **Type hints**: All public functions must have type annotations. Run `mypy` to verify.
+- **Docstrings**: Follow Google style or NumPy style; include parameters, returns, and exceptions.
+
+**Example `pyproject.toml` snippet:**
+```toml
+[project.optional-dependencies]
+dev = ["pytest>=7.0", "mypy>=1.0", "black>=23.0", "ruff>=0.1.0"]
+
+[tool.black]
+line-length = 88
+
+[tool.ruff]
+select = ["E", "F", "W", "I"]
+fixable = ["I"]
+```
+
+## Testing
+- We use `pytest` for unit tests.
+- **All new features must include tests**. Bug fixes should include a regression test.
+- Mock external HTTP requests using `responses` or `pytest-httpx` to avoid hitting real URLs during tests.
+- Run the test suite locally:
+  ```bash
+  pytest tests/
+  ```
+- Ensure test coverage does not decrease. If possible, run:
+  ```bash
+  pytest --cov=open_news tests/
+  ```
+
+## Submitting Pull Requests
+1. **Create a new branch** from `main` with a descriptive name (`fix-google-date-parsing` or `add-timeout-option`).
+2. **Make your changes**, following the coding standards.
+3. **Add or update tests** and documentation (README, docstrings).
+4. **Run the test suite** and ensure it passes.
+5. **Push your branch** and open a Pull Request (PR) against the `main` branch.
+6. In the PR description, include:
+   - What the PR does.
+   - Any related issue numbers (e.g., "Fixes #42").
+   - Screenshots or logs if relevant.
+7. A maintainer will review your PR. Please be responsive to feedback.
+
+### PR Checklist
+- [ ] Code is formatted with Black.
+- [ ] Linter (Ruff) reports no errors.
+- [ ] Type hints added and `mypy` passes.
+- [ ] New tests are included and pass.
+- [ ] Documentation updated (if applicable).
+- [ ] PR targets `main` and has no merge conflicts.
+
+## Questions?
+If you’re unsure about anything, feel free to open a Discussion or ask in an existing issue thread. We’re happy to help you get started!
+
+**Thank you for helping make `open-news` better!** 🚀

open_news_api-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 open-news
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

open_news_api-0.1.1/MANIFEST.in

@@ -0,0 +1,8 @@
+include README.md
+include LICENSE
+include requirements.txt
+include CHANGELOG.md
+include CODE_OF_CONDUCT.md
+include CONTRIBUTING.md
+recursive-exclude __pycache__ *
+recursive-exclude *.pyc