content-core 0.1.0__tar.gz → 0.1.2__tar.gz

content_core-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# Contributing to Content-Core
+
+Thank you for your interest in contributing to Content-Core! This guide will help you get started with the contribution process.
+
+## Code of Conduct
+
+In the interest of fostering an open and welcoming environment, we expect all contributors to be respectful and considerate of others. By participating in this project, you agree to:
+
+- Be respectful of different viewpoints and experiences
+- Gracefully accept constructive criticism
+- Focus on what is best for the community
+- Show empathy towards other community members
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+- Ensure the bug was not already reported by searching on GitHub under [Issues](https://github.com/lfnovo/content-core/issues).
+- If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/lfnovo/content-core/issues/new).
+- Include a clear title and description.
+- Add as much relevant information as possible, including:
+  - Steps to reproduce the issue
+  - Expected behavior
+  - Actual behavior
+  - System details (OS, Python version, etc.)
+
+### Suggesting Enhancements
+
+- Open an issue with the tag "enhancement" to suggest new features or improvements.
+- Clearly describe the enhancement and its benefits.
+
+### Code Contributions
+
+1. **Fork the Repo**: Fork the project repository to your own GitHub account.
+2. **Clone the Repo**: Clone the forked repository to your local machine.
+3. **Create a Branch**: Create a branch with a descriptive name related to the feature or bug you're working on.
+4. **Make Changes**: Make your changes to the codebase. Ensure your code follows the project's coding style and conventions.
+5. **Test Your Changes**: Make sure your changes pass all tests. Add tests if you're introducing new functionality.
+6. **Commit Your Changes**: Commit your changes with a clear and descriptive commit message.
+7. **Push to Your Fork**: Push your changes to your forked repository.
+8. **Submit a Pull Request**: Create a pull request from your fork to the main project repository. Provide a clear description of your changes and why they are needed.
+
+### Pull Request Guidelines
+
+- Ensure your PR addresses a single issue or feature.
+- Update documentation if your changes affect it.
+- Reference related issues in your PR description.
+- Be prepared to make changes based on feedback from maintainers.
+
+## Development Setup
+
+To set up the development environment:
+
+1. Install Python 3.10 or later.
+2. Install `uv` for package management:
+   ```bash
+   curl -LsSf https://astral.sh/uv/install.sh | sh
+   ```
+3. Clone the repository and navigate to the project directory.
+4. Create a virtual environment and install dependencies:
+   ```bash
+   uv venv
+   uv sync
+   ```
+5. Run tests to ensure everything is set up correctly:
+   ```bash
+   uv run pytest
+   ```
+
+## Coding Style
+
+We follow PEP 8 for Python code. Please ensure your code adheres to these guidelines. Use tools like `flake8` or `pylint` to check your code style.
+
+## License
+
+By contributing to Content-Core, you agree that your contributions will be licensed under the [MIT License](LICENSE).
+
+Thank you for contributing to Content-Core and helping make it better!

content_core-0.1.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Luis Novo
+
+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.

{content_core-0.1.0 → content_core-0.1.2}/PKG-INFO

@@ -1,10 +1,11 @@
 Metadata-Version: 2.4
 Name: content-core
-Version: 0.1.0
+Version: 0.1.2
 Summary: Extract what matters from any media source
 Author-email: LUIS NOVO <lfnovo@gmail.com>
+License-File: LICENSE
 Requires-Python: >=3.10
-Requires-Dist: aiohttp>=3.11.16
+Requires-Dist: aiohttp>=3.11
 Requires-Dist: bs4>=0.0.2
 Requires-Dist: dicttoxml>=1.7.16
 Requires-Dist: esperanto>=1.2.0
@@ -243,8 +244,10 @@ make lint
 make help
 ```
 
+## License
+
+This project is licensed under the [MIT License](LICENSE). See the [LICENSE](LICENSE) file for details.
+
 ## Contributing
-Contributions are welcome! Please follow standard practices (fork, feature branch, pull request).
 
-## License
-This project is licensed under the MIT License - see the LICENSE file for details.
+Contributions are welcome! Please see our [Contributing Guide](CONTRIBUTING.md) for more details on how to get started.

{content_core-0.1.0 → content_core-0.1.2}/README.md

@@ -215,8 +215,10 @@ make lint
 make help
 ```
 
+## License
+
+This project is licensed under the [MIT License](LICENSE). See the [LICENSE](LICENSE) file for details.
+
 ## Contributing
-Contributions are welcome! Please follow standard practices (fork, feature branch, pull request).
 
-## License
-This project is licensed under the MIT License - see the LICENSE file for details.
+Contributions are welcome! Please see our [Contributing Guide](CONTRIBUTING.md) for more details on how to get started.

{content_core-0.1.0 → content_core-0.1.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "content-core"
-version = "0.1.0"
+version = "0.1.2"
 description = "Extract what matters from any media source"
 readme = "README.md"
 authors = [
@@ -8,7 +8,7 @@ authors = [
 ]
 requires-python = ">=3.10"
 dependencies = [
-    "aiohttp>=3.11.16",
+    "aiohttp>=3.11",
     "bs4>=0.0.2",
     "esperanto>=1.2.0",
     "google-genai>=1.10.0",

{content_core-0.1.0 → content_core-0.1.2}/src/content_core/processors/youtube.py

@@ -156,4 +156,5 @@ async def extract_youtube_transcript(state: ProcessSourceState):
     return {
         "content": formatter.format_transcript(transcript),
         "title": title,
+        "metadata": {"video_id": video_id, "transcript": transcript.to_raw_data()},
     }

{content_core-0.1.0 → content_core-0.1.2}/uv.lock

@@ -354,7 +354,7 @@ wheels = [
 
 [[package]]
 name = "content-core"
-version = "0.1.0"
+version = "0.1.2"
 source = { editable = "." }
 dependencies = [
     { name = "aiohttp" },
@@ -390,7 +390,7 @@ dev = [
 
 [package.metadata]
 requires-dist = [
-    { name = "aiohttp", specifier = ">=3.11.16" },
+    { name = "aiohttp", specifier = ">=3.11" },
     { name = "bs4", specifier = ">=0.0.2" },
     { name = "dicttoxml", specifier = ">=1.7.16" },
     { name = "esperanto", specifier = ">=1.2.0" },