| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 2e7e82b commit 71bd080
2 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1 +1 @@ | |||
| 1 | - 2.1.13 | ||
| 1 | + 3.0.0 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2,6 +2,22 @@ | |||
| 2 | 2 | Changelog | |
| 3 | 3 | ========= | |
| 4 | 4 | ||
| 5 | + 3.0.0 - Remove Python 2 support | ||
| 6 | + =============================== | ||
| 7 | + | ||
| 8 | + Motivation for this is a patch which improves unicode handling when dealing with filesystem paths. | ||
| 9 | + Python 2 compatibility was introduced to deal with differences, and I thought it would be a good idea | ||
| 10 | + to 'just' drop support right now, mere 5 months away from the official maintenance stop of python 2.7. | ||
| 11 | + | ||
| 12 | + The underlying motivation clearly is my anger when thinking python and unicode, which was a hassle from the | ||
| 13 | + start, at least in a codebase as old as GitPython, which totally doesn't handle encodings correctly in many cases. | ||
| 14 | + | ||
| 15 | + Having migrated to using `Rust` exclusively for tooling, I still see that correct handling of encodings isn't entirely | ||
| 16 | + trivial, but at least `Rust` makes clear what has to be done at compile time, allowing to write software that is pretty | ||
| 17 | + much guaranteed to work once it compiles. | ||
| 18 | + | ||
| 19 | + Again, my apologies if removing Python 2 support caused inconveniences, please see release 2.1.13 which returns it. | ||
| 20 | + | ||
| 5 | 21 | 2.1.13 - Bring back Python 2.7 support | |
| 6 | 22 | ====================================== | |
| 7 | 23 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments