You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,10 @@ Any and all advice, support, PR's, etc are welcome and would be greatly apprecia
12
12
13
13
14
14
# Why does this project exist?
15
-
Unfortunately the [Hypermodern Python Cookiecutter] is no longer maintained nor modern.
15
+
Unfortunately, the [Hypermodern Python Cookiecutter] is no longer maintained nor modern.
16
16
While it will always have a place in my heart, there have been far too many improvements in Python tooling to keep using it as is.
17
17
18
-
For a whle I maintained [a personal fork](https://github.com/56kyle/cookiecutter-hypermodern-python) that I would update, however when it came time to switch
18
+
For a while I maintained [a personal fork](https://github.com/56kyle/cookiecutter-hypermodern-python) that I would update, however when it came time to switch
19
19
to new tooling such as [ruff], [uv], [maturin], etc, I found the process of updating the existing tooling to be extremly painful.
20
20
21
21
The [Hypermodern Python Cookiecutter] remains as a fantastic sendoff point for devs interested in building a 2021 style Python Package, but there were
@@ -34,7 +34,7 @@ The [Robust Python Cookiecutter] exists to solve a few main concerns
34
34
One of the main issues I encountered with [my personal fork] of the [Hypermodern Python Cookiecutter] was that any change
35
35
I made to my repos would mean a later conflict if I tried to rerun [cookiecutter] to sync a change from a different project.
36
36
37
-
Thankfully [cruft] exists specifically to help with this issue. It enables us to periodically create PR's to add in any fixes
37
+
Thankfully,[cruft] exists specifically to help with this issue. It enables us to periodically create PR's to add in any fixes
38
38
the [Robust Python Cookiecutter] may have added.
39
39
40
40
Additionally, extra care is put in to use tooling specific config files whenever possible to help reduce merge conflicts occurring
@@ -76,12 +76,12 @@ Overall it's rather rare that people debate over tooling for no reason. Most thi
76
76
77
77
## CI/CD Vendor Lock
78
78
Now don't get me wrong, I love [github-actions] and do pretty much everything in my power to avoid [bitbucket-pipelines].
79
-
However not all jobs have the luxury of github, and I would love to be able to just use the same template for both my personal and professional projects.
79
+
However, not all jobs have the luxury of github, and I would love to be able to just use the same template for both my personal and professional projects.
80
80
81
81
The [Robust Python Cookiecutter] focuses on being as modular as possible for areas that connect to the CI/CD pipeline. Additionally, there will always be either alternative
82
82
CI/CD options or at a minimum basic examples of what the translated CI/CD pipeline would look like.
83
83
84
-
Finally the main reason that this task is even possible is that the [Robust Python Cookiecutter] mirrors all of the CI/CD steps in it's local dev tooling.
84
+
Finally, the main reason that this task is even possible is that the [Robust Python Cookiecutter] mirrors all of the CI/CD steps in it's local dev tooling.
85
85
The local [noxfile] is designed to match up directly with the CI/CD each step of the way.
86
86
87
87
The [Hypermodern Python Cookiecutter] did this where it could afford to also, however the lack of [uv] meant it would significantly increase CI/CD times if done everywhere.
0 commit comments