tratto-email 0.2.0__tar.gz

tratto_email-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,49 @@
+name: CI
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main, develop]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.10', '3.11', '3.12']
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v5
+        with: { python-version: '${{ matrix.python-version }}' }
+      - run: pip install -e ".[dev]"
+      - run: pytest --cov=tratto --cov-report=term-missing
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.12' }
+      - run: pip install ruff mypy
+      - run: ruff check tratto
+      - run: mypy tratto
+
+  build:
+    runs-on: ubuntu-latest
+    needs: [test, lint]
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.12' }
+      - run: pip install hatchling build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          retention-days: 7

tratto_email-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,20 @@
+name: Publish
+
+on:
+  push:
+    tags: ['v*']
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.12' }
+      - run: pip install build
+      - run: python -m build
+      - name: Publish to PyPI (trusted publishing)
+        uses: pypa/gh-action-pypi-publish@release/v1

tratto_email-0.2.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.pyc
+*.pyo
+*.egg-info/
+dist/
+build/
+.venv/
+.env
+.DS_Store
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+htmlcov/
+.coverage

tratto_email-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,127 @@
+# 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 with this Code of Conduct, and will communicate reasons
+for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces (issues, pull
+requests, discussions, and any other project-related communication), and
+also applies when an individual is officially representing the community in
+public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**conduct@tratto.email**. 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].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla]: https://github.com/mozilla/diversity

tratto_email-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,168 @@
+# Contributing to tratto-python
+
+Thank you for helping improve the official Tratto Python SDK! This guide covers
+everything you need to get started contributing.
+
+---
+
+## Code of Conduct
+
+Be respectful and constructive. We follow the
+[Contributor Covenant v2.1](./CODE_OF_CONDUCT.md).
+
+---
+
+## Ways to contribute
+
+- **Bug reports** — open an issue with steps to reproduce, expected behaviour, and actual behaviour.
+- **Feature requests** — open an issue describing the use-case before writing code.
+- **Pull requests** — see the workflow below.
+- **Documentation** — typos, clarifications, and extra examples are always welcome.
+
+---
+
+## Development setup
+
+**Requirements:** Python 3.10+, `pip`.
+
+```bash
+# 1. Fork the repository on GitHub, then clone your fork
+git clone https://github.com/<your-username>/tratto-python.git
+cd tratto-python
+
+# 2. Create a virtual environment
+python -m venv .venv
+source .venv/bin/activate   # Windows: .venv\Scripts\activate
+
+# 3. Install the package in editable mode with dev dependencies
+pip install -e ".[dev]"
+```
+
+---
+
+## Running the tests
+
+```bash
+pytest
+```
+
+With coverage report:
+
+```bash
+pytest --cov=tratto --cov-report=term-missing
+```
+
+Tests live in `tests/` and **must not make real network requests** — use
+`unittest.mock.patch` to mock `urllib.request.urlopen`.
+
+---
+
+## Linting and type checking
+
+```bash
+# Style
+ruff check tratto tests
+
+# Types
+mypy tratto
+```
+
+All checks must pass before a PR is merged.
+
+---
+
+## Pull request workflow
+
+1. **Open an issue first** (except for trivial fixes like typos).
+2. Fork and create a feature branch:
+   ```bash
+   git checkout -b feat/your-feature
+   ```
+3. Make your changes. Keep commits focused and descriptive.
+4. Add or update tests for every changed behaviour.
+5. Run `pytest`, `ruff check`, and `mypy tratto` locally — fix any failures.
+6. Push your branch and open a PR against `main`.
+
+### PR checklist
+
+- [ ] Tests added or updated
+- [ ] `ruff check tratto tests` passes
+- [ ] `mypy tratto` passes
+- [ ] Public API changes reflected in `README.md`
+
+---
+
+## Project structure
+
+```
+tratto-python/
+├── tratto/
+│   ├── __init__.py          # public exports
+│   ├── _http.py             # internal HTTP client
+│   ├── client.py            # Tratto main class
+│   ├── types.py             # option dataclasses + TrattoError
+│   └── resources/
+│       ├── __init__.py
+│       ├── emails.py
+│       ├── contacts.py
+│       ├── audiences.py
+│       ├── templates.py
+│       ├── domains.py
+│       ├── campaigns.py
+│       └── webhooks.py
+├── tests/
+│   └── test_client.py
+├── pyproject.toml
+├── README.md
+├── CONTRIBUTING.md
+└── LICENSE
+```
+
+---
+
+## Coding conventions
+
+- **No external runtime dependencies.** The SDK uses only Python's standard library.
+- **Python 3.10+** — use native generics (`list[str]`, `dict[str, str]`, `str | None`).
+- **Strict type hints** on all public functions and methods (enforced by `mypy --strict`).
+- **Dataclasses for option objects** — one per write operation, matching the API body.
+- **snake_case** in Python maps to **camelCase** in JSON request bodies and responses.
+- **Resource sub-clients** — each API resource group has its own class in `tratto/resources/`.
+- Follow `ruff` defaults for code style (line length 100).
+- Do not add `print` statements or logging to the SDK.
+
+---
+
+## Versioning
+
+This SDK follows [Semantic Versioning](https://semver.org/):
+
+| Bump | When |
+|---|---|
+| **Patch** (`0.x.y`) | Bug fixes, non-breaking improvements |
+| **Minor** (`0.x.0`) | New API coverage, new optional fields |
+| **Major** (`x.0.0`) | Breaking changes to the public API |
+
+When cutting a release, update:
+- `__version__` in `tratto/__init__.py`
+- `_SDK_VERSION` in `tratto/_http.py`
+- `version` in `pyproject.toml`
+
+---
+
+## Release process (maintainers only)
+
+1. Bump the version in the three files above.
+2. Commit and merge to `main`.
+3. Push a tag:
+   ```bash
+   git tag v0.x.y && git push --tags
+   ```
+4. GitHub Actions publishes to PyPI automatically via the `publish` workflow.
+
+---
+
+## License
+
+By contributing you agree that your work will be licensed under the
+[MIT License](./LICENSE).

tratto_email-0.2.0/LICENSE

@@ -0,0 +1,20 @@
+MIT License
+
+Copyright (c) 2025 Tratto
+
+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urnished 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.