-
-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preserve unicode when slugifying by default #797
Conversation
Codecov Report
@@ Coverage Diff @@
## master #797 +/- ##
==========================================
+ Coverage 92.91% 92.94% +0.02%
==========================================
Files 9 9
Lines 720 723 +3
Branches 140 141 +1
==========================================
+ Hits 669 672 +3
Misses 34 34
Partials 17 17
Continue to review full report at Codecov.
|
43420de
to
2626e23
Compare
@lucemia would you be able to review thise changeset? given this is a pretty big change (in few lines of code of course) I do want to have at least one review from someone else |
Would love to, but I am not reviewer of this repo... is there a way to become a reviewer? |
Two options:
|
I joined Jazzband! thanks your advice |
#798 this PR seems to indicate another important change that might be necessary here: |
8b0dd4c
to
db41c60
Compare
This change is motivated by the many many people using non-latin languages who experience the (rather baffling) behavior of outright stripping characters when generating slugs from stuff that doesn't fit into ASCII. We went through loads of pain as a programming community to get to nicely supporting unicode everywhere, it's time to take advantage of that fact and just let people have stuff appear in their native language as much as possible.
Alright I made sure that |
I checked the PR, it looks good to me! |
The next release of django-taggit [will change slugs to allow_unicode=True](jazzband/django-taggit#797), which breaks our check for missing migrations. This change is not released yet, but the fix is needed now so that we can run against django-taggit git master for our tests against Django main. It's also dependent on the version bump happening at the django-taggit end: jazzband/django-taggit#800
* Fix test migrations for django-taggit 3.0.0 (forthcoming) The next release of django-taggit [will change slugs to allow_unicode=True](jazzband/django-taggit#797), which breaks our check for missing migrations. This change is not released yet, but the fix is needed now so that we can run against django-taggit git master for our tests against Django main. It's also dependent on the version bump happening at the django-taggit end: jazzband/django-taggit#800 * Allow django-taggit 3.x as a dependency and drop special case when testing against Django main
Are you aware that the test case here is broken with Python 3.8? |
@jsonn Python 3.8 is within the test suite and is passing, do you have a stack trace showing failure that can be tracked down here? |
|
Thanks to @hwshim810 (for original implementation) and @lucemia
(for ping + pointing out the perf weirdness) from #572 for motivating this.
This change is motivated by the many many people using non-latin
languages who experience the (rather baffling) behavior of outright
stripping characters when generating slugs from stuff that doesn't
fit into ASCII.
We went through loads of pain as a programming community to get to
nicely supporting unicode everywhere, it's time to take advantage of
that fact and just let people have stuff appear in their native
language as much as possible.