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
This error was caused by a Python bug on Windows. It's been fixed by [this PR](https://github.com/python/cpython/pull/22017), and according to Python's changelog, [3.8.6rc1](https://docs.python.org/3.8/whatsnew/changelog.html#python-3-8-6-release-candidate-1) and [3.9.0rc2](https://docs.python.org/3.9/whatsnew/changelog.html#python-3-9-0-release-candidate-2) should be the accurate versions first contain this fix. In conclusion, upgrade your Python version might solve this issue.
87
87
88
88
More discussion can be found in issue [#318](https://github.com/commitizen-tools/commitizen/issues/318).
89
+
90
+
## Why does commitizen not support CalVer?
91
+
92
+
`commitizen` could support CalVer alongside SemVer, but in practice implementing CalVer
93
+
creates numerous edge cases that are difficult to maintain (#385) and more generally
94
+
mixing the two version schemes may not be a good idea. If CalVer or other custom
95
+
versioning scheme is needed, `commitizen` could still be used to standardize commits
96
+
and create changelogs, but a separate package should be used for version increments.
97
+
98
+
Mixing CalVer and SemVer is generally not recommended because each versioning scheme
99
+
serves a different purposes. Diverging from either specification can be confusing to
100
+
users and cause errors when third party tools that don't expect the non-standard format.
101
+
102
+
In the future, `commitizen` may support some implementation of CalVer, but at the time
103
+
of writing, there are no plans to implement the feature (#173).
104
+
105
+
If you would like to learn more about both schemes, there are plenty of good resources:
0 commit comments