pytailwindcss 0.2.0__tar.gz → 0.3.1__tar.gz

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

@@ -0,0 +1,50 @@
+# This workflow will install Python dependencies, run tests and lint with a variety of Python versions
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions
+
+name: Run tests
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  tests:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: [ "3.11", "3.12", "3.13", "3.14" ]
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: uv sync
+      - name: Test with pytest
+        run: uv run pytest
+
+  release:
+    needs: [ tests ]
+    if: success() && startsWith(github.ref, 'refs/tags/')
+    runs-on: ubuntu-24.04
+    environment: release
+
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          python-version: '3.11'
+
+      - name: Build
+        run: uv build
+
+      - uses: pypa/gh-action-pypi-publish@release/v1

pytailwindcss-0.3.1/.github/workflows/pre-commit.yml

@@ -0,0 +1,18 @@
+name: pre-commit
+
+on:
+  pull_request:
+  push:
+    branches: [ main ]
+
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v2
+      - uses: pre-commit/action@v3.0.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}

pytailwindcss-0.3.1/.gitignore

@@ -0,0 +1,145 @@
+# 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
+src/tests/build
+.claude
+.history

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

@@ -0,0 +1,36 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.4.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-yaml
+      - id: debug-statements
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: mixed-line-ending
+      - id: requirements-txt-fixer
+  - repo: https://github.com/psf/black
+    rev: 23.3.0
+    hooks:
+      - id: black
+        args: [ --line-length=119 ]
+  - repo: https://github.com/pycqa/isort
+    rev: 5.12.0
+    hooks:
+      - id: isort
+        args: [ "--profile", "black", "--filter-files" ]
+  - repo: https://github.com/PyCQA/flake8
+    rev: 6.0.0
+    hooks:
+      - id: flake8
+        additional_dependencies:
+          - flake8-bugbear
+          - flake8-comprehensions
+          - flake8-tidy-imports
+          - flake8-typing-imports

pytailwindcss-0.3.1/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: pytailwindcss
+Version: 0.3.1
+Summary: Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js.
+Project-URL: Homepage, https://github.com/timonweb/pytailwindcss
+Author-email: Tim Kamanin <tim@timonweb.com>
+License: MIT
+License-File: LICENSE
+Keywords: cli,css,tailwind
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+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
+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 recently announced a new 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`:
+
+   ```bash
+   pip install pytailwindcss
+   ```
+
+2. **[Recommended]** Preinstall the `tailwindcss` binary:
+
+   ```bash
+   tailwindcss_install
+   ```
+
+   By default, the latest binary version will be downloaded. To pin to a specific Tailwind CSS version, set the `TAILWINDCSS_VERSION` environment variable before running the command:
+
+   ```bash
+   # In a Dockerfile
+   ENV TAILWINDCSS_VERSION=v4.1.16
+   RUN tailwindcss_install
+
+   # On Linux/macOS
+   export TAILWINDCSS_VERSION=v4.1.16
+   tailwindcss_install
+
+   # On Windows (cmd)
+   set TAILWINDCSS_VERSION=v4.1.16
+   tailwindcss_install
+
+   # On Windows (PowerShell)
+   $env:TAILWINDCSS_VERSION="v4.1.16"
+   tailwindcss_install
+   ```
+
+   To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
+
+   If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
+
+3. The `tailwindcss` command should now be available in your terminal. Try running it:
+
+   ```bash
+   tailwindcss
+   ```
+
+   You should see the help output for the `tailwindcss` command. If you skipped step 2, the binary will be downloaded automatically on this first run. Use `tailwindcss` to create a new project or work with an existing *Tailwind CSS* project.
+
+4. Create a new *Tailwind CSS* project by navigating to your project directory and initializing it:
+
+   ```bash
+   tailwindcss init
+   ```
+
+   This command creates the default *tailwind.config.js* file.
+
+5. Start a watcher to compile CSS automatically during development:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --watch
+   ```
+
+6. Compile and minify your CSS for production:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --minify
+   ```
+
+That's it! For more information on using *Tailwind CSS* and its CLI, refer to the [official Tailwind CSS documentation](https://tailwindcss.com/docs).
+
+## Caveats
+
+While this approach simplifies your setup, there are some trade-offs. Without *Node.js*, you won't be able to install third-party plugins or additional dependencies for your *Tailwind CSS* setup. However, this might not be a dealbreaker for most use cases.
+
+You can still customize *Tailwind CSS* via the *tailwind.config.js* file, and the standalone build includes all official *Tailwind CSS* plugins: `@tailwindcss/aspect-ratio`, `@tailwindcss/forms`, `@tailwindcss/line-clamp`, and `@tailwindcss/typography`. This covers approximately 90% of typical *Tailwind CSS* usage scenarios.
+
+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.
+
+## 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 - 2025 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)

pytailwindcss-0.3.1/README.md

@@ -0,0 +1,112 @@
+# 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 recently announced a new 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`:
+
+   ```bash
+   pip install pytailwindcss
+   ```
+
+2. **[Recommended]** Preinstall the `tailwindcss` binary:
+
+   ```bash
+   tailwindcss_install
+   ```
+
+   By default, the latest binary version will be downloaded. To pin to a specific Tailwind CSS version, set the `TAILWINDCSS_VERSION` environment variable before running the command:
+
+   ```bash
+   # In a Dockerfile
+   ENV TAILWINDCSS_VERSION=v4.1.16
+   RUN tailwindcss_install
+
+   # On Linux/macOS
+   export TAILWINDCSS_VERSION=v4.1.16
+   tailwindcss_install
+
+   # On Windows (cmd)
+   set TAILWINDCSS_VERSION=v4.1.16
+   tailwindcss_install
+
+   # On Windows (PowerShell)
+   $env:TAILWINDCSS_VERSION="v4.1.16"
+   tailwindcss_install
+   ```
+
+   To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
+
+   If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
+
+3. The `tailwindcss` command should now be available in your terminal. Try running it:
+
+   ```bash
+   tailwindcss
+   ```
+
+   You should see the help output for the `tailwindcss` command. If you skipped step 2, the binary will be downloaded automatically on this first run. Use `tailwindcss` to create a new project or work with an existing *Tailwind CSS* project.
+
+4. Create a new *Tailwind CSS* project by navigating to your project directory and initializing it:
+
+   ```bash
+   tailwindcss init
+   ```
+
+   This command creates the default *tailwind.config.js* file.
+
+5. Start a watcher to compile CSS automatically during development:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --watch
+   ```
+
+6. Compile and minify your CSS for production:
+
+   ```bash
+   tailwindcss -i input.css -o output.css --minify
+   ```
+
+That's it! For more information on using *Tailwind CSS* and its CLI, refer to the [official Tailwind CSS documentation](https://tailwindcss.com/docs).
+
+## Caveats
+
+While this approach simplifies your setup, there are some trade-offs. Without *Node.js*, you won't be able to install third-party plugins or additional dependencies for your *Tailwind CSS* setup. However, this might not be a dealbreaker for most use cases.
+
+You can still customize *Tailwind CSS* via the *tailwind.config.js* file, and the standalone build includes all official *Tailwind CSS* plugins: `@tailwindcss/aspect-ratio`, `@tailwindcss/forms`, `@tailwindcss/line-clamp`, and `@tailwindcss/typography`. This covers approximately 90% of typical *Tailwind CSS* usage scenarios.
+
+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.
+
+## 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 - 2025 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)

pytailwindcss-0.3.1/pyproject.toml

@@ -0,0 +1,43 @@
+[project]
+name = "pytailwindcss"
+version = "0.3.1"
+description = "Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js."
+authors = [{ name = "Tim Kamanin", email = "tim@timonweb.com" }]
+readme = "README.md"
+license = { text = "MIT" }
+keywords = ["cli", "tailwind", "css"]
+requires-python = ">=3.11"
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Operating System :: OS Independent",
+    "Topic :: Software Development :: Libraries",
+    "Topic :: Utilities",
+    "Environment :: Web Environment"
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/timonweb/pytailwindcss"
+
+[project.scripts]
+tailwindcss = "pytailwindcss.__main__:main"
+tailwindcss_install = "pytailwindcss.__main__:install"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.0.3",
+    "pre-commit>=4.6.0",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/pytailwindcss"]

{pytailwindcss-0.2.0 → pytailwindcss-0.3.1}/src/pytailwindcss/utils.py

@@ -9,7 +9,7 @@ def make_subprocess_run_kwargs(cwd=None, env=None, live_output=False):
     """
     opts = {
         "cwd": cwd or os.getcwd(),
-        "env": env or {},
+        "env": env or None,
     }
     if live_output is False:
         opts.update(

pytailwindcss-0.3.1/tests/contexts.py

@@ -0,0 +1,22 @@
+import os
+import shutil
+from contextlib import contextmanager
+
+
+@contextmanager
+def clean_dir(path):
+    delete_anything(path)
+    try:
+        yield
+    finally:
+        delete_anything(path)
+
+
+def delete_anything(path):
+    path = str(path)
+    if not os.path.exists(path):
+        return None
+
+    if os.path.isfile(path):
+        return os.remove(path)
+    return shutil.rmtree(path)

pytailwindcss-0.3.1/tests/test_core.py

@@ -0,0 +1,38 @@
+import pytest
+
+import pytailwindcss
+from pytailwindcss.exceptions import PyTailwindCssBinaryNotFound
+from pytailwindcss.utils import get_bin_path
+
+from .contexts import clean_dir
+
+
+def test_successful_run():
+    """
+    It installs the executable and successfully runs the CLI.
+    """
+    with clean_dir(get_bin_path()):
+        pytailwindcss.install()
+        output = pytailwindcss.run("--help")
+        assert "tailwindcss" in output.lower()
+
+
+def test_successful_run_from_custom_bin_path():
+    """
+    It installs the executable and successfully runs the CLI from a custom path.
+    """
+    ALTERNATIVE_BIN_PATH = "/tmp/test-bin/tailwindcss"
+
+    with clean_dir(ALTERNATIVE_BIN_PATH):
+        pytailwindcss.install(bin_path=ALTERNATIVE_BIN_PATH)
+        output = pytailwindcss.run("--help", bin_path=ALTERNATIVE_BIN_PATH)
+        assert "tailwindcss" in output.lower()
+
+
+def test_unsuccessful_run():
+    """
+    It fails to run build command because executable is not installed.
+    """
+    with clean_dir(get_bin_path()):
+        with pytest.raises(PyTailwindCssBinaryNotFound):
+            pytailwindcss.run("build")