pytailwindcss 0.2.0__tar.gz → 0.3.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. pytailwindcss-0.3.0/PKG-INFO +138 -0
  2. pytailwindcss-0.3.0/README.md +112 -0
  3. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/pyproject.toml +8 -7
  4. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/utils.py +1 -1
  5. pytailwindcss-0.2.0/PKG-INFO +0 -125
  6. pytailwindcss-0.2.0/README.md +0 -97
  7. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/LICENSE +0 -0
  8. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/__init__.py +0 -0
  9. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/__main__.py +0 -0
  10. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/exceptions.py +0 -0
  11. {pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/installation.py +0 -0
pytailwindcss-0.3.0/PKG-INFO ADDED
@@ -0,0 +1,138 @@
1
+ Metadata-Version: 2.4
2
+ Name: pytailwindcss
3
+ Version: 0.3.0
4
+ Summary: Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js.
5
+ License: MIT
6
+ License-File: LICENSE
7
+ Keywords: cli,tailwind,css
8
+ Author: Tim Kamanin
9
+ Author-email: tim@timonweb.com
10
+ Requires-Python: >=3.11,<4.0
11
+ Classifier: Development Status :: 4 - Beta
12
+ Classifier: Environment :: Web Environment
13
+ Classifier: Intended Audience :: Developers
14
+ Classifier: License :: OSI Approved :: MIT License
15
+ Classifier: Operating System :: OS Independent
16
+ Classifier: Programming Language :: Python :: 3
17
+ Classifier: Programming Language :: Python :: 3.11
18
+ Classifier: Programming Language :: Python :: 3.12
19
+ Classifier: Programming Language :: Python :: 3.13
20
+ Classifier: Programming Language :: Python :: 3.14
21
+ Classifier: Topic :: Software Development :: Libraries
22
+ Classifier: Topic :: Utilities
23
+ Project-URL: Homepage, https://github.com/timonweb/pytailwindcss
24
+ Description-Content-Type: text/markdown
25
+
26
+ # Standalone Tailwind CSS CLI, installable via pip
27
+
28
+ Use *Tailwind CSS* without *Node.js* — install it via pip.
29
+
30
+ ## Why
31
+
32
+ *Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
33
+ in your team, your Docker container, or your inner circle.
34
+
35
+ The *Tailwind CSS* team recently announced a new standalone CLI build that gives you the full power of *Tailwind CLI* in
36
+ a self-contained executable — no *Node.js* or `npm` required.
37
+
38
+ However, installing the standalone CLI isn't as easy as running `npm install`.
39
+
40
+ 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:
41
+
42
+ ```bash
43
+ pip install pytailwindcss
44
+ ```
45
+
46
+ Now you can run `tailwindcss` in your terminal:
47
+
48
+ ```bash
49
+ tailwindcss -i input.css -o output.css --minify
50
+ ```
51
+
52
+ Voilà!
53
+
54
+ ## Get started
55
+
56
+ 1. Install `pytailwindcss` via `pip`:
57
+
58
+ ```bash
59
+ pip install pytailwindcss
60
+ ```
61
+
62
+ 2. **[Recommended]** Preinstall the `tailwindcss` binary:
63
+
64
+ ```bash
65
+ tailwindcss_install
66
+ ```
67
+
68
+ 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:
69
+
70
+ ```bash
71
+ # In a Dockerfile
72
+ ENV TAILWINDCSS_VERSION=v4.1.16
73
+ RUN tailwindcss_install
74
+
75
+ # On Linux/macOS
76
+ export TAILWINDCSS_VERSION=v4.1.16
77
+ tailwindcss_install
78
+
79
+ # On Windows (cmd)
80
+ set TAILWINDCSS_VERSION=v4.1.16
81
+ tailwindcss_install
82
+
83
+ # On Windows (PowerShell)
84
+ $env:TAILWINDCSS_VERSION="v4.1.16"
85
+ tailwindcss_install
86
+ ```
87
+
88
+ To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
89
+
90
+ If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
91
+
92
+ 3. The `tailwindcss` command should now be available in your terminal. Try running it:
93
+
94
+ ```bash
95
+ tailwindcss
96
+ ```
97
+
98
+ 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.
99
+
100
+ 4. Create a new *Tailwind CSS* project by navigating to your project directory and initializing it:
101
+
102
+ ```bash
103
+ tailwindcss init
104
+ ```
105
+
106
+ This command creates the default *tailwind.config.js* file.
107
+
108
+ 5. Start a watcher to compile CSS automatically during development:
109
+
110
+ ```bash
111
+ tailwindcss -i input.css -o output.css --watch
112
+ ```
113
+
114
+ 6. Compile and minify your CSS for production:
115
+
116
+ ```bash
117
+ tailwindcss -i input.css -o output.css --minify
118
+ ```
119
+
120
+ That's it! For more information on using *Tailwind CSS* and its CLI, refer to the [official Tailwind CSS documentation](https://tailwindcss.com/docs).
121
+
122
+ ## Caveats
123
+
124
+ 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.
125
+
126
+ 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.
127
+
128
+ Here's what the *Tailwind CSS* team says about the standalone build:
129
+ > 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.
130
+
131
+ ## Bugs and Suggestions
132
+
133
+ Found a bug or have a suggestion? Please use the issue tracker on GitHub:
134
+
135
+ [https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
136
+
137
+ 2021 - 2025 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)
138
+
pytailwindcss-0.3.0/README.md ADDED
@@ -0,0 +1,112 @@
1
+ # Standalone Tailwind CSS CLI, installable via pip
2
+
3
+ Use *Tailwind CSS* without *Node.js* — install it via pip.
4
+
5
+ ## Why
6
+
7
+ *Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
8
+ in your team, your Docker container, or your inner circle.
9
+
10
+ The *Tailwind CSS* team recently announced a new standalone CLI build that gives you the full power of *Tailwind CLI* in
11
+ a self-contained executable — no *Node.js* or `npm` required.
12
+
13
+ However, installing the standalone CLI isn't as easy as running `npm install`.
14
+
15
+ 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:
16
+
17
+ ```bash
18
+ pip install pytailwindcss
19
+ ```
20
+
21
+ Now you can run `tailwindcss` in your terminal:
22
+
23
+ ```bash
24
+ tailwindcss -i input.css -o output.css --minify
25
+ ```
26
+
27
+ Voilà!
28
+
29
+ ## Get started
30
+
31
+ 1. Install `pytailwindcss` via `pip`:
32
+
33
+ ```bash
34
+ pip install pytailwindcss
35
+ ```
36
+
37
+ 2. **[Recommended]** Preinstall the `tailwindcss` binary:
38
+
39
+ ```bash
40
+ tailwindcss_install
41
+ ```
42
+
43
+ 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:
44
+
45
+ ```bash
46
+ # In a Dockerfile
47
+ ENV TAILWINDCSS_VERSION=v4.1.16
48
+ RUN tailwindcss_install
49
+
50
+ # On Linux/macOS
51
+ export TAILWINDCSS_VERSION=v4.1.16
52
+ tailwindcss_install
53
+
54
+ # On Windows (cmd)
55
+ set TAILWINDCSS_VERSION=v4.1.16
56
+ tailwindcss_install
57
+
58
+ # On Windows (PowerShell)
59
+ $env:TAILWINDCSS_VERSION="v4.1.16"
60
+ tailwindcss_install
61
+ ```
62
+
63
+ To see a list of available Tailwind CSS releases, visit: https://github.com/tailwindlabs/tailwindcss/releases
64
+
65
+ If you skip this step, the binary will be downloaded automatically on the first run of the `tailwindcss` command.
66
+
67
+ 3. The `tailwindcss` command should now be available in your terminal. Try running it:
68
+
69
+ ```bash
70
+ tailwindcss
71
+ ```
72
+
73
+ 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.
74
+
75
+ 4. Create a new *Tailwind CSS* project by navigating to your project directory and initializing it:
76
+
77
+ ```bash
78
+ tailwindcss init
79
+ ```
80
+
81
+ This command creates the default *tailwind.config.js* file.
82
+
83
+ 5. Start a watcher to compile CSS automatically during development:
84
+
85
+ ```bash
86
+ tailwindcss -i input.css -o output.css --watch
87
+ ```
88
+
89
+ 6. Compile and minify your CSS for production:
90
+
91
+ ```bash
92
+ tailwindcss -i input.css -o output.css --minify
93
+ ```
94
+
95
+ That's it! For more information on using *Tailwind CSS* and its CLI, refer to the [official Tailwind CSS documentation](https://tailwindcss.com/docs).
96
+
97
+ ## Caveats
98
+
99
+ 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.
100
+
101
+ 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.
102
+
103
+ Here's what the *Tailwind CSS* team says about the standalone build:
104
+ > 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.
105
+
106
+ ## Bugs and Suggestions
107
+
108
+ Found a bug or have a suggestion? Please use the issue tracker on GitHub:
109
+
110
+ [https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
111
+
112
+ 2021 - 2025 (c) Tim Kamanin — [A Full-Stack Django and Wagtail Developer](https://timonweb.com)
{pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [tool.poetry]
2
2
  name = "pytailwindcss"
3
- version = "0.2.0"
3
+ version = "0.3.0"
4
4
  description = "Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js."
5
5
  authors = ["Tim Kamanin <tim@timonweb.com>"]
6
6
  homepage = "https://github.com/timonweb/pytailwindcss"
@@ -11,9 +11,10 @@ classifiers = [
11
11
  "Development Status :: 4 - Beta",
12
12
  "Intended Audience :: Developers",
13
13
  "License :: OSI Approved :: MIT License",
14
- "Programming Language :: Python :: 3.8",
15
- "Programming Language :: Python :: 3.9",
16
- "Programming Language :: Python :: 3.10",
14
+ "Programming Language :: Python :: 3.11",
15
+ "Programming Language :: Python :: 3.12",
16
+ "Programming Language :: Python :: 3.13",
17
+ "Programming Language :: Python :: 3.14",
17
18
  "Operating System :: OS Independent",
18
19
  "Topic :: Software Development :: Libraries",
19
20
  "Topic :: Utilities",
@@ -29,11 +30,11 @@ tailwindcss = "pytailwindcss.__main__:main"
29
30
  tailwindcss_install = "pytailwindcss.__main__:install"
30
31
 
31
32
  [tool.poetry.dependencies]
32
- python = "^3.8"
33
+ python = "^3.11"
33
34
 
34
35
  [tool.poetry.dev-dependencies]
35
- pytest = "^7.4.0"
36
- pre-commit = "^3.3.0"
36
+ pytest = "^8.4.2"
37
+ pre-commit = "^4.3.0"
37
38
 
38
39
  [build-system]
39
40
  requires = ["poetry-core>=1.0.0"]
{pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/src/pytailwindcss/utils.py RENAMED
@@ -9,7 +9,7 @@ def make_subprocess_run_kwargs(cwd=None, env=None, live_output=False):
9
9
  """
10
10
  opts = {
11
11
  "cwd": cwd or os.getcwd(),
12
- "env": env or {},
12
+ "env": env or None,
13
13
  }
14
14
  if live_output is False:
15
15
  opts.update(
pytailwindcss-0.2.0/PKG-INFO DELETED
@@ -1,125 +0,0 @@
1
- Metadata-Version: 2.1
2
- Name: pytailwindcss
3
- Version: 0.2.0
4
- Summary: Standalone Tailwind CSS CLI, installable via pip. Use Tailwind CSS without Node.js.
5
- Home-page: https://github.com/timonweb/pytailwindcss
6
- License: MIT
7
- Keywords: cli,tailwind,css
8
- Author: Tim Kamanin
9
- Author-email: tim@timonweb.com
10
- Requires-Python: >=3.8,<4.0
11
- Classifier: Development Status :: 4 - Beta
12
- Classifier: Environment :: Web Environment
13
- Classifier: Intended Audience :: Developers
14
- Classifier: License :: OSI Approved :: MIT License
15
- Classifier: Operating System :: OS Independent
16
- Classifier: Programming Language :: Python :: 3
17
- Classifier: Programming Language :: Python :: 3.8
18
- Classifier: Programming Language :: Python :: 3.9
19
- Classifier: Programming Language :: Python :: 3.10
20
- Classifier: Programming Language :: Python :: 3.11
21
- Classifier: Programming Language :: Python :: 3.10
22
- Classifier: Programming Language :: Python :: 3.8
23
- Classifier: Programming Language :: Python :: 3.9
24
- Classifier: Topic :: Software Development :: Libraries
25
- Classifier: Topic :: Utilities
26
- Description-Content-Type: text/markdown
27
-
28
- # Standalone Tailwind CSS CLI, installable via pip
29
-
30
- Use *Tailwind CSS* without *Node.js* and install it via pip.
31
-
32
- ## Why
33
-
34
- *Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
35
- in your team, your Docker container, or your inner circle.
36
-
37
- The *Tailwind CSS* team recently announced a new standalone CLI build that gives you the full power of *Tailwind CLI* in
38
- a self-contained executable — no *Node.js* or `npm` required.
39
-
40
- However, installing such a standalone CLI isn't as easy as running `npm install`, the installation command for *Node.js*
41
- .
42
-
43
- That's why I decided to make it as simple as running `pip install` command. As a result you can install the standalone *
44
- Tailwind CLI* via `pip` by running the following command:
45
-
46
- ```bash
47
- pip install pytailwindcss
48
- ```
49
-
50
- Now you can run `tailwindcss` in your terminal as:
51
-
52
- ```
53
- tailwindcss -i input.css -o output.css --minify
54
- ```
55
-
56
- Voila!
57
-
58
- ## Get started
59
-
60
- 1. Install `tailwindcss` via `pip` by executing the following command:
61
-
62
- ```
63
- pip install pytailwindcss
64
- ```
65
-
66
- 2. [Optional] Preinstall `tailwindcss` binary by running the following command:
67
-
68
- ```
69
- tailwindcss_install
70
- ```
71
-
72
- If you skip this step, the binary will be downloaded on the first run of `tailwindcss` command.
73
-
74
- 3. The `tailwindcss` command should now be available in your terminal. Try to run it:
75
-
76
- ```
77
- tailwindcss
78
- ```
79
-
80
- If the installation was successful, you should see the message about binary being downloaded on the first run. When download is complete, you should see the help output for the `tailwindcss` command. Use `tailwindcss`
81
- to create a new project or work with an existing *Tailwind CSS* project.
82
-
83
- 4. Let's create a new project. Go to the directory where you want to host your *Tailwind CSS* project and initialize it
84
- by running:
85
-
86
- ```
87
- tailwindcss init
88
- ```
89
-
90
- This command will create the default *tailwind.config.js* file.
91
-
92
- 5. Start a watcher by running:
93
-
94
- ```
95
- tailwindcss -i input.css -o output.css --watch
96
- ```
97
-
98
- 6. Compile and minify your CSS for production by running:
99
-
100
- ```
101
- tailwindcss -i input.css -o output.css --minify
102
- ```
103
-
104
- You got it. Please refer to [official Tailwind documentation](https://tailwindcss.com/docs) for more information on
105
- using *Tailwind CSS* and its CLI.
106
-
107
- ## Caveats
108
-
109
- It's not all roses, though. Giving up *Node.js* means you won't be able to install plugins or additional dependencies for
110
- your *Tailwind CSS* setup. At the same time, that might not be a dealbreaker. You can still customize *Tailwind CSS* via
111
- the *tailwind.config.js* file. And the standalone build also comes with all official *Tailwind CSS* plugins
112
- like `@tailwindcss/aspect-ratio`, `@tailwindcss/forms`, `@tailwindcss/line-clamp`, and `@tailwindcss/typography`. So in
113
- 90% of *Tailwind CSS* usage cases you should be covered, and the setup is so simplified now.
114
-
115
- Here is what the *Tailwind CSS* team says about going the standalone *Tailwind CSS* route:
116
- > 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.
117
-
118
- ## Bugs and suggestions
119
-
120
- If you have found a bug, please use the issue tracker on GitHub.
121
-
122
- [https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
123
-
124
- 2021 (c) [Tim Kamanin - A Full Stack Django and Wagtail Developer](https://timonweb.com)
125
-
pytailwindcss-0.2.0/README.md DELETED
@@ -1,97 +0,0 @@
1
- # Standalone Tailwind CSS CLI, installable via pip
2
-
3
- Use *Tailwind CSS* without *Node.js* and install it via pip.
4
-
5
- ## Why
6
-
7
- *Tailwind CSS* is notoriously dependent on *Node.js*. If you're a *Python* developer, this dependency may not be welcome
8
- in your team, your Docker container, or your inner circle.
9
-
10
- The *Tailwind CSS* team recently announced a new standalone CLI build that gives you the full power of *Tailwind CLI* in
11
- a self-contained executable — no *Node.js* or `npm` required.
12
-
13
- However, installing such a standalone CLI isn't as easy as running `npm install`, the installation command for *Node.js*
14
- .
15
-
16
- That's why I decided to make it as simple as running `pip install` command. As a result you can install the standalone *
17
- Tailwind CLI* via `pip` by running the following command:
18
-
19
- ```bash
20
- pip install pytailwindcss
21
- ```
22
-
23
- Now you can run `tailwindcss` in your terminal as:
24
-
25
- ```
26
- tailwindcss -i input.css -o output.css --minify
27
- ```
28
-
29
- Voila!
30
-
31
- ## Get started
32
-
33
- 1. Install `tailwindcss` via `pip` by executing the following command:
34
-
35
- ```
36
- pip install pytailwindcss
37
- ```
38
-
39
- 2. [Optional] Preinstall `tailwindcss` binary by running the following command:
40
-
41
- ```
42
- tailwindcss_install
43
- ```
44
-
45
- If you skip this step, the binary will be downloaded on the first run of `tailwindcss` command.
46
-
47
- 3. The `tailwindcss` command should now be available in your terminal. Try to run it:
48
-
49
- ```
50
- tailwindcss
51
- ```
52
-
53
- If the installation was successful, you should see the message about binary being downloaded on the first run. When download is complete, you should see the help output for the `tailwindcss` command. Use `tailwindcss`
54
- to create a new project or work with an existing *Tailwind CSS* project.
55
-
56
- 4. Let's create a new project. Go to the directory where you want to host your *Tailwind CSS* project and initialize it
57
- by running:
58
-
59
- ```
60
- tailwindcss init
61
- ```
62
-
63
- This command will create the default *tailwind.config.js* file.
64
-
65
- 5. Start a watcher by running:
66
-
67
- ```
68
- tailwindcss -i input.css -o output.css --watch
69
- ```
70
-
71
- 6. Compile and minify your CSS for production by running:
72
-
73
- ```
74
- tailwindcss -i input.css -o output.css --minify
75
- ```
76
-
77
- You got it. Please refer to [official Tailwind documentation](https://tailwindcss.com/docs) for more information on
78
- using *Tailwind CSS* and its CLI.
79
-
80
- ## Caveats
81
-
82
- It's not all roses, though. Giving up *Node.js* means you won't be able to install plugins or additional dependencies for
83
- your *Tailwind CSS* setup. At the same time, that might not be a dealbreaker. You can still customize *Tailwind CSS* via
84
- the *tailwind.config.js* file. And the standalone build also comes with all official *Tailwind CSS* plugins
85
- like `@tailwindcss/aspect-ratio`, `@tailwindcss/forms`, `@tailwindcss/line-clamp`, and `@tailwindcss/typography`. So in
86
- 90% of *Tailwind CSS* usage cases you should be covered, and the setup is so simplified now.
87
-
88
- Here is what the *Tailwind CSS* team says about going the standalone *Tailwind CSS* route:
89
- > 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.
90
-
91
- ## Bugs and suggestions
92
-
93
- If you have found a bug, please use the issue tracker on GitHub.
94
-
95
- [https://github.com/timonweb/pytailwindcss/issues](https://github.com/timonweb/pytailwindcss/issues)
96
-
97
- 2021 (c) [Tim Kamanin - A Full Stack Django and Wagtail Developer](https://timonweb.com)
{pytailwindcss-0.2.0 → pytailwindcss-0.3.0}/LICENSE RENAMED
File without changes