-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error with unicode module names on Python2 #9
Comments
Thanks, will dig it soon. Do you have any fix for yourself? |
Not really… For starters we just dropped Python 2 support (cause it's not needed in house). But that's temporary, cause we would like to keep 2.7 supported. I'm not sure, if So, just workarounds for now. I was thinking about monkey–patching and "byteify" the relevant parts… but not sure where to start and what's relevant. |
Hi, I got this working. Damn this Here's the change itself: https://github.com/sobolevn/django-split-settings/blob/d3d1afb3bbab117ab4479537f170056f6c4a809a/split_settings/tools.py#L91 It won't probably work on This is your example, I guess: Basic |
Thanks for the fast fix! While we will wait with re–enabling Python 2 support for your next release, I ran the latest Github version in some test environments and it works. |
Nice, I will release it soon. |
* Now supporting `unicode` filenames, fixes #9 * Tests structure is changed * Removed example * Changed how `MANIFEST.in` is defined
I maintain a Django installation and want to migrate the settings (lots of
from X import *
) to django-split-setings. Seems everything went fine, but the tox test for Python 2.7 (the only tested version < 3) bailed on me with the following error:This might be a result of
from __future__ import unicode_literals
. Any ideas how to handle this?The text was updated successfully, but these errors were encountered: