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
We have been using awesome-slugify for quite some time now, due to very handy helpers like slugify_url and its handling of unicode/chinese characters.
v0.13 of transifex-client now installs python-slugify which also uses the same module name slugify, causing a conflict. On our production systems the transifex client is not installed, so this isn't causing an issue, however in our dev environment it is.
Not sure what can be done about this, short of offering an option like pip install transifex[awesome-slugify] or having the projects re-namespace (as they should have before now!).
I will look into changing which slugify we use, but then we may run into issues where I peg to a lower version and then transifex-client requires a newer one.
The text was updated successfully, but these errors were encountered:
We had the same issue, its a problem with python dependency management (which is a hell anyways).
I think transifex should implement their own slug function instead of depending on an external library.
I think they should vendor this dependency at least. We've moved onto
python_slugify too now, so not as big an issue.
The main problem, small one, is that the pinned versions of slugify and six
are *old*, and we use newer ones. I just ignore the warning, but it would
be good if they had broader versions allowed, since people don't usually
use tfx standalone, but rather part of s larger project and are likely to
have these packages installed as well.
On Sat, Mar 23, 2019, 14:20 Tjerk Wolterink ***@***.***> wrote:
We had the same issue, its a problem with python dependency management
(which is a hell anyways).
I think transifex should implement their own slug function instead of
depending on an external library.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGToi2toWjmnDkGoIOfGevLR3t_1c1Dks5vZhv6gaJpZM4S2YVM>
.
We have been using awesome-slugify for quite some time now, due to very handy helpers like
slugify_url
and its handling of unicode/chinese characters.v0.13 of
transifex-client
now installs python-slugify which also uses the same module nameslugify
, causing a conflict. On our production systems the transifex client is not installed, so this isn't causing an issue, however in our dev environment it is.Not sure what can be done about this, short of offering an option like
pip install transifex[awesome-slugify]
or having the projects re-namespace (as they should have before now!).I will look into changing which slugify we use, but then we may run into issues where I peg to a lower version and then
transifex-client
requires a newer one.The text was updated successfully, but these errors were encountered: