pytailwindcss 0.3.0__tar.gz → 0.4.0__tar.gz

pytailwindcss-0.4.0/.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    cooldown:
+      default-days: 7
+    groups:
+      actions:
+        patterns:
+          - "*"

pytailwindcss-0.4.0/.github/workflows/ci.yml

@@ -0,0 +1,83 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@v10.3.0
+        with:
+          python-version: '3.14'
+      - run: uvx pre-commit run --all-files --show-diff-on-failure
+
+  tests:
+    needs: [ pre-commit ]
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ ubuntu-latest ]
+        python-version: [ "3.11", "3.12", "3.13", "3.14" ]
+        include:
+          # Binary selection is OS-specific, so the newest Python also runs on macOS and Windows.
+          - os: macos-latest
+            python-version: "3.14"
+          - os: windows-latest
+            python-version: "3.14"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@v10.3.0
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync --locked
+      - run: uv run pytest --cov --cov-report=term
+
+  tests-alpine:
+    needs: [ pre-commit ]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      # JavaScript actions can't run inside Alpine containers (the runner's Node is glibc-only),
+      # so the musl test run happens through a plain `docker run`. Tailwind's musl builds link
+      # against libstdc++ and libgcc, which Alpine doesn't ship by default.
+      - run: >-
+          docker run --rm -v "$PWD:/src" -w /src -e UV_PYTHON_DOWNLOADS=never python:3.14-alpine
+          sh -c "apk add --no-cache libstdc++ libgcc && pip install --root-user-action=ignore uv && uv sync --locked && uv run pytest"
+
+  release:
+    needs: [ tests, tests-alpine ]
+    if: success() && startsWith(github.ref, 'refs/tags/')
+    runs-on: ubuntu-24.04
+    environment: release
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@v10.3.0
+        with:
+          python-version: '3.14'
+      - name: Check tag matches project version
+        run: test "${GITHUB_REF_NAME#v}" = "$(uv version --short)"
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1

pytailwindcss-0.4.0/.github/zizmor.yml

@@ -0,0 +1,6 @@
+rules:
+  unpinned-uses:
+    config:
+      # Major-version tags kept current by Dependabot, rather than SHA pins.
+      policies:
+        "*": ref-pin

pytailwindcss-0.4.0/.gitignore

@@ -0,0 +1,146 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$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
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.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/
+
+.DS_Store
+.idea
+src/pytailwindcss/bin
+.claude
+.history
+
+_devcontext/

pytailwindcss-0.4.0/.pre-commit-config.yaml

@@ -0,0 +1,41 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-added-large-files
+      - id: check-ast
+      - id: check-case-conflict
+      - id: check-json
+      - id: check-merge-conflict
+      - id: check-symlinks
+      - id: check-toml
+      - id: check-yaml
+      - id: debug-statements
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: mixed-line-ending
+  - repo: https://github.com/crate-ci/typos
+    rev: v1.51.1
+    hooks:
+      - id: typos
+  - repo: https://github.com/tox-dev/pyproject-fmt
+    rev: v2.30.3
+    hooks:
+      - id: pyproject-fmt
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.17.0
+    hooks:
+      - id: ruff-check
+        args: [ --fix, --show-fixes ]
+      - id: ruff-format
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v2.4.0
+    hooks:
+      - id: mypy
+        additional_dependencies:
+          - pytest>=9.0.3
+  - repo: https://github.com/zizmorcore/zizmor-pre-commit
+    rev: v1.30.1
+    hooks:
+      - id: zizmor

pytailwindcss-0.4.0/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+## 0.4.0 (2026-10-13)
+
+### Added
+
+- Downloads are verified against the release's `sha256sums.txt`; a mismatch raises `PyTailwindCssChecksumMismatch` and nothing is installed. Releases without checksums (before v4) install with a warning.
+- Alpine and other musl-based Linux systems get the `-musl` Tailwind CSS binary (it needs `apk add libstdc++ libgcc`).
+- `TAILWINDCSS_BIN_DIR` environment variable to choose where binaries are stored.
+- Type hints and a `py.typed` marker.
+
+### Changed
+
+- Installation is atomic: the binary is downloaded next to its destination and swapped in only after it's verified, so a failed download keeps the previous binary.
+- Installed binaries are mode `0755`, so a binary installed as root (e.g. at Docker build time) runs for any user.
+- Download progress is printed to stderr instead of stdout, so it no longer mixes with `tailwindcss` output.
+- Network failures, HTTP errors other than 404, unsupported platforms, and unwritable binary directories raise `PyTailwindCssException` with a readable message; the CLI commands print it instead of a traceback.
+- Downloads time out after 60 seconds without data.
+- `run()` raises `PyTailwindCssBinaryNotFound` only when the binary is actually missing; a missing `cwd` now surfaces as the original `FileNotFoundError`.
+- README updated for Tailwind CSS v4.
+
+### Fixed
+
+- Windows: the binary is saved as `tailwindcss.exe`, so it can be executed.
+- `run(bin_path="...", auto_install=True)` no longer crashes when `bin_path` is a string.
+- Temporary download directories are no longer leaked.
+
+## Earlier releases
+
+See the [git tags](https://github.com/timonweb/pytailwindcss/tags).

pytailwindcss-0.4.0/PKG-INFO

@@ -0,0 +1,191 @@
+Metadata-Version: 2.5
+Name: pytailwindcss
+Version: 0.4.0
+Summary: Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js.
+Project-URL: Changelog, https://github.com/timonweb/pytailwindcss/blob/main/CHANGELOG.md
+Project-URL: Homepage, https://github.com/timonweb/pytailwindcss
+Project-URL: Issues, https://github.com/timonweb/pytailwindcss/issues
+Project-URL: Source, https://github.com/timonweb/pytailwindcss
+Author-email: Tim Kamanin <tim@timonweb.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: cli,css,tailwind
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# Standalone Tailwind CSS CLI, installable via pip
+
+Use *Tailwind CSS* without *Node.js* — install it via pip.
+
+## Why
+
+*Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
+in your team, your Docker container, or your inner circle.
+
+The *Tailwind CSS* team ships a standalone CLI build that gives you the full power of *Tailwind CLI* in a
+self-contained executable — no *Node.js* or `npm` required.
+
+However, installing the standalone CLI isn't as easy as running `npm install`.
+
+That's why I created this package to make it as simple as running the `pip install` command. Now you can install the standalone *Tailwind CLI* via `pip` by running:
+
+```bash
+pip install pytailwindcss
+```
+
+Now you can run `tailwindcss` in your terminal:
+
+```bash
+tailwindcss -i input.css -o output.css --minify
+```
+
+Voilà!
+
+## Get started
+
+1. Install `pytailwindcss` via `pip` (or `uv add pytailwindcss`):
+
+   ```bash
+   pip install pytailwindcss
+   ```
+
+2. **[Recommended]** Preinstall the `tailwindcss` binary:
+
+   ```bash
+   tailwindcss_install
+   ```
+
+   If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
+
+3. Create an `input.css` file that imports Tailwind CSS:
+
+   ```css
+   @import "tailwindcss";
+   ```
+
+   Tailwind CSS v4 is configured right in your CSS — there's no `tailwind.config.js` and no `tailwindcss init` anymore. See the [official documentation](https://tailwindcss.com/docs) for theming and customization.
+
+4. Start a watcher to compile CSS automatically during development:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --watch
+   ```
+
+5. Compile and minify your CSS for production:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --minify
+   ```
+
+That's it! Run `tailwindcss --help` to see all the CLI options.
+
+## Pinning a Tailwind CSS version
+
+By default, the latest binary version is downloaded. To pin to a specific Tailwind CSS version, set the `TAILWINDCSS_VERSION` environment variable. It's used by both `tailwindcss_install` and `tailwindcss`:
+
+```bash
+# On Linux/macOS
+export TAILWINDCSS_VERSION=v4.3.3
+tailwindcss_install
+
+# On Windows (cmd)
+set TAILWINDCSS_VERSION=v4.3.3
+tailwindcss_install
+
+# On Windows (PowerShell)
+$env:TAILWINDCSS_VERSION="v4.3.3"
+tailwindcss_install
+```
+
+To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
+
+Every download is checked against the SHA-256 checksums published with the release, and a binary that doesn't match is never installed. Releases before v4 don't publish checksums; for those, `pytailwindcss` logs a warning and installs the binary unverified.
+
+## Where the binary lives
+
+Binaries are stored per version inside the installed package, so every virtualenv gets its own copy and projects don't affect each other.
+
+If that directory isn't writable (for example, a virtualenv owned by another user), point `TAILWINDCSS_BIN_DIR` at a directory you can write to (relative paths and `~` are resolved):
+
+```bash
+export TAILWINDCSS_BIN_DIR=~/.cache/pytailwindcss
+```
+
+Binaries then go to `$TAILWINDCSS_BIN_DIR/<version>/tailwindcss`.
+
+## Docker
+
+Install the binary while building the image, so containers start without downloading anything:
+
+```dockerfile
+ENV TAILWINDCSS_VERSION=v4.3.3
+RUN pip install pytailwindcss && tailwindcss_install
+```
+
+The binary is readable and executable by every user, so it's fine to install it as root and run your app as an unprivileged user.
+
+On Alpine (musl) images, `pytailwindcss` downloads the matching `-musl` build of Tailwind CSS v4. That build needs the C++ runtime libraries, which Alpine doesn't include by default:
+
+```dockerfile
+RUN apk add --no-cache libstdc++ libgcc
+```
+
+## Using it from Python
+
+```python
+import pytailwindcss
+
+# Download the binary (optional, see auto_install below).
+pytailwindcss.install(version="v4.3.3")
+
+# Run the CLI and get its output as a string.
+pytailwindcss.run("-i input.css -o output.css --minify", version="v4.3.3")
+
+# Arguments can be a list too; auto_install downloads the binary if it's missing.
+pytailwindcss.run(["-i", "input.css", "-o", "output.css"], auto_install=True)
+```
+
+`run()` raises `subprocess.CalledProcessError` when Tailwind CSS exits with an error. Pass `live_output=True` to stream Tailwind's output to the terminal instead; you then get the `subprocess.CompletedProcess` back. Download and installation problems raise subclasses of `pytailwindcss.exceptions.PyTailwindCssException`.
+
+## Caveats
+
+Without *Node.js*, you can't install third-party plugins from npm. The standalone build bundles the official plugins, though — `@tailwindcss/forms`, `@tailwindcss/typography`, and `@tailwindcss/aspect-ratio` — so you can enable them in your CSS:
+
+```css
+@import "tailwindcss";
+@plugin "@tailwindcss/typography";
+```
+
+This covers the vast majority of typical *Tailwind CSS* setups.
+
+Here's what the *Tailwind CSS* team says about the standalone build:
+> If you're working on a project where you don't otherwise need *Node.js* or `npm`, the standalone build can be a great choice. If Tailwind was the only reason you had a package.json file, this is probably going to feel like a nicer solution.
+
+## Development
+
+```bash
+uv sync                       # create the virtualenv with dev dependencies
+uv run pytest                 # run all tests (some download real binaries)
+uv run pytest -m "not network"  # skip the tests that need network access
+uvx pre-commit install        # run linters, formatters, and mypy on every commit
+```
+
+## Bugs and Suggestions
+
+Found a bug or have a suggestion? Please use the issue tracker on GitHub:
+
+[https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
+
+2021 - 2026 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)

pytailwindcss-0.4.0/README.md

@@ -0,0 +1,164 @@
+# Standalone Tailwind CSS CLI, installable via pip
+
+Use *Tailwind CSS* without *Node.js* — install it via pip.
+
+## Why
+
+*Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
+in your team, your Docker container, or your inner circle.
+
+The *Tailwind CSS* team ships a standalone CLI build that gives you the full power of *Tailwind CLI* in a
+self-contained executable — no *Node.js* or `npm` required.
+
+However, installing the standalone CLI isn't as easy as running `npm install`.
+
+That's why I created this package to make it as simple as running the `pip install` command. Now you can install the standalone *Tailwind CLI* via `pip` by running:
+
+```bash
+pip install pytailwindcss
+```
+
+Now you can run `tailwindcss` in your terminal:
+
+```bash
+tailwindcss -i input.css -o output.css --minify
+```
+
+Voilà!
+
+## Get started
+
+1. Install `pytailwindcss` via `pip` (or `uv add pytailwindcss`):
+
+   ```bash
+   pip install pytailwindcss
+   ```
+
+2. **[Recommended]** Preinstall the `tailwindcss` binary:
+
+   ```bash
+   tailwindcss_install
+   ```
+
+   If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
+
+3. Create an `input.css` file that imports Tailwind CSS:
+
+   ```css
+   @import "tailwindcss";
+   ```
+
+   Tailwind CSS v4 is configured right in your CSS — there's no `tailwind.config.js` and no `tailwindcss init` anymore. See the [official documentation](https://tailwindcss.com/docs) for theming and customization.
+
+4. Start a watcher to compile CSS automatically during development:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --watch
+   ```
+
+5. Compile and minify your CSS for production:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --minify
+   ```
+
+That's it! Run `tailwindcss --help` to see all the CLI options.
+
+## Pinning a Tailwind CSS version
+
+By default, the latest binary version is downloaded. To pin to a specific Tailwind CSS version, set the `TAILWINDCSS_VERSION` environment variable. It's used by both `tailwindcss_install` and `tailwindcss`:
+
+```bash
+# On Linux/macOS
+export TAILWINDCSS_VERSION=v4.3.3
+tailwindcss_install
+
+# On Windows (cmd)
+set TAILWINDCSS_VERSION=v4.3.3
+tailwindcss_install
+
+# On Windows (PowerShell)
+$env:TAILWINDCSS_VERSION="v4.3.3"
+tailwindcss_install
+```
+
+To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
+
+Every download is checked against the SHA-256 checksums published with the release, and a binary that doesn't match is never installed. Releases before v4 don't publish checksums; for those, `pytailwindcss` logs a warning and installs the binary unverified.
+
+## Where the binary lives
+
+Binaries are stored per version inside the installed package, so every virtualenv gets its own copy and projects don't affect each other.
+
+If that directory isn't writable (for example, a virtualenv owned by another user), point `TAILWINDCSS_BIN_DIR` at a directory you can write to (relative paths and `~` are resolved):
+
+```bash
+export TAILWINDCSS_BIN_DIR=~/.cache/pytailwindcss
+```
+
+Binaries then go to `$TAILWINDCSS_BIN_DIR/<version>/tailwindcss`.
+
+## Docker
+
+Install the binary while building the image, so containers start without downloading anything:
+
+```dockerfile
+ENV TAILWINDCSS_VERSION=v4.3.3
+RUN pip install pytailwindcss && tailwindcss_install
+```
+
+The binary is readable and executable by every user, so it's fine to install it as root and run your app as an unprivileged user.
+
+On Alpine (musl) images, `pytailwindcss` downloads the matching `-musl` build of Tailwind CSS v4. That build needs the C++ runtime libraries, which Alpine doesn't include by default:
+
+```dockerfile
+RUN apk add --no-cache libstdc++ libgcc
+```
+
+## Using it from Python
+
+```python
+import pytailwindcss
+
+# Download the binary (optional, see auto_install below).
+pytailwindcss.install(version="v4.3.3")
+
+# Run the CLI and get its output as a string.
+pytailwindcss.run("-i input.css -o output.css --minify", version="v4.3.3")
+
+# Arguments can be a list too; auto_install downloads the binary if it's missing.
+pytailwindcss.run(["-i", "input.css", "-o", "output.css"], auto_install=True)
+```
+
+`run()` raises `subprocess.CalledProcessError` when Tailwind CSS exits with an error. Pass `live_output=True` to stream Tailwind's output to the terminal instead; you then get the `subprocess.CompletedProcess` back. Download and installation problems raise subclasses of `pytailwindcss.exceptions.PyTailwindCssException`.
+
+## Caveats
+
+Without *Node.js*, you can't install third-party plugins from npm. The standalone build bundles the official plugins, though — `@tailwindcss/forms`, `@tailwindcss/typography`, and `@tailwindcss/aspect-ratio` — so you can enable them in your CSS:
+
+```css
+@import "tailwindcss";
+@plugin "@tailwindcss/typography";
+```
+
+This covers the vast majority of typical *Tailwind CSS* setups.
+
+Here's what the *Tailwind CSS* team says about the standalone build:
+> If you're working on a project where you don't otherwise need *Node.js* or `npm`, the standalone build can be a great choice. If Tailwind was the only reason you had a package.json file, this is probably going to feel like a nicer solution.
+
+## Development
+
+```bash
+uv sync                       # create the virtualenv with dev dependencies
+uv run pytest                 # run all tests (some download real binaries)
+uv run pytest -m "not network"  # skip the tests that need network access
+uvx pre-commit install        # run linters, formatters, and mypy on every commit
+```
+
+## Bugs and Suggestions
+
+Found a bug or have a suggestion? Please use the issue tracker on GitHub:
+
+[https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
+
+2021 - 2026 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)