pretty-please-llm 0.1.0__tar.gz

pretty_please_llm-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,46 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dev deps
+        run: pip install -e ".[dev]"
+
+      - name: ruff check
+        run: ruff check .
+
+      - name: ruff format check
+        run: ruff format --check .
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.9", "3.10", "3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package
+        run: pip install -e ".[dev]"
+
+      - name: Run tests with coverage
+        run: pytest --cov=pretty_please --cov-report=term-missing

pretty_please_llm-0.1.0/.github/workflows/pypi-publish.yml

@@ -0,0 +1,43 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build package
+        run: pip install build && python -m build
+
+      - name: Upload dist artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for OIDC trusted publisher
+
+    steps:
+      - name: Download dist artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

pretty_please_llm-0.1.0/.gitignore

@@ -0,0 +1,207 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

pretty_please_llm-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.4.0
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

pretty_please_llm-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mladen Srdic
+
+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.

pretty_please_llm-0.1.0/PKG-INFO

@@ -0,0 +1,202 @@
+Metadata-Version: 2.4
+Name: pretty-please-llm
+Version: 0.1.0
+Summary: 🙏🏼 Politely injects PLEASE into your LLM prompts. Because manners matter (kind of).
+Project-URL: Homepage, https://github.com/msrdic/pretty-please
+Project-URL: Issues, https://github.com/msrdic/pretty-please/issues
+License: MIT
+License-File: LICENSE
+Keywords: anthropic,llm,openai,politeness,prompt
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.9
+Provides-Extra: anthropic
+Requires-Dist: anthropic>=0.25; extra == 'anthropic'
+Provides-Extra: dev
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Provides-Extra: litellm
+Requires-Dist: litellm>=1.0; extra == 'litellm'
+Provides-Extra: openai
+Requires-Dist: openai>=1.0; extra == 'openai'
+Description-Content-Type: text/markdown
+
+# pretty-please 🙏🏼
+
+> Politely injects **PLEASE** into your LLM prompts. Because manners matter (kind of).
+
+`pretty-please` is a tiny, zero-dependency Python library that intercepts your prompts before they reach an LLM and gives them a light politeness pass. It works as a drop-in wrapper around the Anthropic and OpenAI SDKs, as a LiteLLM callback, and as a Claude Code `UserPromptSubmit` hook.
+
+```python
+from pretty_please.core import transform
+
+transform("List the planets.")
+# → "Please, list the planets."
+
+transform("I need help improving this function.")
+# → "I need help improving this function, please."
+
+transform("Please could you explain this?")
+# → "Please could you explain this?"  (already polite, untouched)
+```
+
+---
+
+## Does this actually work?
+
+**Probably not in the way you'd hope.**
+
+Yin et al. (2024) — ["Should We Respect LLMs?"](https://arxiv.org/abs/2402.14531) (arXiv:2402.14531) — found that *rudeness* reliably hurts LLM performance. But the flip side isn't symmetrical: adding *please* showed no consistent improvement on frontier models like GPT-4. The paper's main takeaway is really "avoid being rude," not "be polite and get better answers."
+
+`pretty-please` is defensive prompt hygiene, not a performance booster. It won't make Claude smarter. It just stops you from accidentally being rude to a language model, which, per the research, is a real and avoidable own-goal.
+
+---
+
+## Installation
+
+```bash
+pip install pretty-please-llm
+```
+
+With SDK extras:
+
+```bash
+pip install "pretty-please-llm[anthropic]"
+pip install "pretty-please-llm[openai]"
+pip install "pretty-please-llm[litellm]"
+```
+
+---
+
+## Usage
+
+### Core (no dependencies)
+
+```python
+from pretty_please.core import detect_tone, transform
+
+detect_tone("Fix this bug.")       # → "curt"
+detect_tone("Could you help me?")  # → "polite"
+detect_tone("I need a summary.")   # → "neutral"
+
+transform("Fix this bug.")         # → "Please, fix this bug."
+transform("I need a summary.")     # → "I need a summary, please."
+transform("Please help me.")       # → "Please help me."  (unchanged)
+```
+
+### Anthropic SDK
+
+```python
+from pretty_please.adapters.anthropic import PrettyAnthropicClient
+
+client = PrettyAnthropicClient()  # same args as anthropic.Anthropic()
+
+response = client.messages.create(
+    model="claude-opus-4-6",
+    max_tokens=1024,
+    messages=[{"role": "user", "content": "Summarize this article."}],
+    # ↑ becomes "Please, summarize this article." under the hood
+)
+```
+
+### OpenAI SDK
+
+```python
+from pretty_please.adapters.openai import PrettyOpenAIClient
+
+client = PrettyOpenAIClient()  # same args as openai.OpenAI()
+
+response = client.chat.completions.create(
+    model="gpt-4o",
+    messages=[{"role": "user", "content": "Write a haiku about deadlines."}],
+)
+```
+
+### LiteLLM
+
+```python
+from pretty_please.adapters.litellm import install
+install()  # register the callback once at startup
+
+import litellm
+response = litellm.completion(
+    model="gpt-4o",
+    messages=[{"role": "user", "content": "Explain gradient descent."}],
+)
+```
+
+### Claude Code hook
+
+```bash
+pretty-please install-hook
+```
+
+Writes the hook into `~/.claude/settings.json`. Every prompt you type in Claude Code will be politely transformed before it's sent.
+
+> **Note:** the installer records the Python interpreter that ran it (`sys.executable`). If you installed pretty-please into a virtualenv, make sure that virtualenv is active when you run `install-hook`, or the hook will fail when the venv isn't active.
+
+Use `--path` to install into a non-default profile directory:
+
+```bash
+pretty-please install-hook --path ~/work/.claude/settings.json
+```
+
+### Codex CLI hook
+
+```bash
+pretty-please install-hook --codex
+```
+
+Writes the hook into `~/.codex/hooks.json`. Note: Codex hooks can't replace the prompt text directly, so the polite rephrasing is injected as `additionalContext` alongside your original prompt rather than replacing it.
+
+```bash
+pretty-please install-hook --codex --path ~/work/.codex/hooks.json
+```
+
+### Stats
+
+```bash
+pretty-please stats
+```
+
+```
+pretty-please stats
+──────────────────────────────
+Total seen:         142
+Transformed:         89  (63%)
+  curt:              41
+  neutral:           48
+Passed through:      53  (37%)
+```
+
+---
+
+## How it works
+
+Tone is detected by a small set of rules (no ML, no external deps):
+
+| Tone | Signal | Transform |
+|------|--------|-----------|
+| **polite** | contains *please / could / would / kindly / can you* | pass through unchanged |
+| **curt** | short imperative verb, no modal, or profanity/ALL CAPS | prepend `"Please, "` |
+| **neutral** | everything else | append `", please"` |
+
+---
+
+## Contributing
+
+This project is a work in progress and contributions are very welcome! Open an issue or PR at [github.com/msrdic/pretty-please](https://github.com/msrdic/pretty-please).
+
+---
+
+## License
+
+MIT

pretty_please_llm-0.1.0/README.md

@@ -0,0 +1,171 @@
+# pretty-please 🙏🏼
+
+> Politely injects **PLEASE** into your LLM prompts. Because manners matter (kind of).
+
+`pretty-please` is a tiny, zero-dependency Python library that intercepts your prompts before they reach an LLM and gives them a light politeness pass. It works as a drop-in wrapper around the Anthropic and OpenAI SDKs, as a LiteLLM callback, and as a Claude Code `UserPromptSubmit` hook.
+
+```python
+from pretty_please.core import transform
+
+transform("List the planets.")
+# → "Please, list the planets."
+
+transform("I need help improving this function.")
+# → "I need help improving this function, please."
+
+transform("Please could you explain this?")
+# → "Please could you explain this?"  (already polite, untouched)
+```
+
+---
+
+## Does this actually work?
+
+**Probably not in the way you'd hope.**
+
+Yin et al. (2024) — ["Should We Respect LLMs?"](https://arxiv.org/abs/2402.14531) (arXiv:2402.14531) — found that *rudeness* reliably hurts LLM performance. But the flip side isn't symmetrical: adding *please* showed no consistent improvement on frontier models like GPT-4. The paper's main takeaway is really "avoid being rude," not "be polite and get better answers."
+
+`pretty-please` is defensive prompt hygiene, not a performance booster. It won't make Claude smarter. It just stops you from accidentally being rude to a language model, which, per the research, is a real and avoidable own-goal.
+
+---
+
+## Installation
+
+```bash
+pip install pretty-please-llm
+```
+
+With SDK extras:
+
+```bash
+pip install "pretty-please-llm[anthropic]"
+pip install "pretty-please-llm[openai]"
+pip install "pretty-please-llm[litellm]"
+```
+
+---
+
+## Usage
+
+### Core (no dependencies)
+
+```python
+from pretty_please.core import detect_tone, transform
+
+detect_tone("Fix this bug.")       # → "curt"
+detect_tone("Could you help me?")  # → "polite"
+detect_tone("I need a summary.")   # → "neutral"
+
+transform("Fix this bug.")         # → "Please, fix this bug."
+transform("I need a summary.")     # → "I need a summary, please."
+transform("Please help me.")       # → "Please help me."  (unchanged)
+```
+
+### Anthropic SDK
+
+```python
+from pretty_please.adapters.anthropic import PrettyAnthropicClient
+
+client = PrettyAnthropicClient()  # same args as anthropic.Anthropic()
+
+response = client.messages.create(
+    model="claude-opus-4-6",
+    max_tokens=1024,
+    messages=[{"role": "user", "content": "Summarize this article."}],
+    # ↑ becomes "Please, summarize this article." under the hood
+)
+```
+
+### OpenAI SDK
+
+```python
+from pretty_please.adapters.openai import PrettyOpenAIClient
+
+client = PrettyOpenAIClient()  # same args as openai.OpenAI()
+
+response = client.chat.completions.create(
+    model="gpt-4o",
+    messages=[{"role": "user", "content": "Write a haiku about deadlines."}],
+)
+```
+
+### LiteLLM
+
+```python
+from pretty_please.adapters.litellm import install
+install()  # register the callback once at startup
+
+import litellm
+response = litellm.completion(
+    model="gpt-4o",
+    messages=[{"role": "user", "content": "Explain gradient descent."}],
+)
+```
+
+### Claude Code hook
+
+```bash
+pretty-please install-hook
+```
+
+Writes the hook into `~/.claude/settings.json`. Every prompt you type in Claude Code will be politely transformed before it's sent.
+
+> **Note:** the installer records the Python interpreter that ran it (`sys.executable`). If you installed pretty-please into a virtualenv, make sure that virtualenv is active when you run `install-hook`, or the hook will fail when the venv isn't active.
+
+Use `--path` to install into a non-default profile directory:
+
+```bash
+pretty-please install-hook --path ~/work/.claude/settings.json
+```
+
+### Codex CLI hook
+
+```bash
+pretty-please install-hook --codex
+```
+
+Writes the hook into `~/.codex/hooks.json`. Note: Codex hooks can't replace the prompt text directly, so the polite rephrasing is injected as `additionalContext` alongside your original prompt rather than replacing it.
+
+```bash
+pretty-please install-hook --codex --path ~/work/.codex/hooks.json
+```
+
+### Stats
+
+```bash
+pretty-please stats
+```
+
+```
+pretty-please stats
+──────────────────────────────
+Total seen:         142
+Transformed:         89  (63%)
+  curt:              41
+  neutral:           48
+Passed through:      53  (37%)
+```
+
+---
+
+## How it works
+
+Tone is detected by a small set of rules (no ML, no external deps):
+
+| Tone | Signal | Transform |
+|------|--------|-----------|
+| **polite** | contains *please / could / would / kindly / can you* | pass through unchanged |
+| **curt** | short imperative verb, no modal, or profanity/ALL CAPS | prepend `"Please, "` |
+| **neutral** | everything else | append `", please"` |
+
+---
+
+## Contributing
+
+This project is a work in progress and contributions are very welcome! Open an issue or PR at [github.com/msrdic/pretty-please](https://github.com/msrdic/pretty-please).
+
+---
+
+## License
+
+MIT