Skip to content
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

as "¶" is non-ascii character, we need to define encoding. #11

Closed
wants to merge 1 commit into from

Conversation

ParvJain
Copy link
Contributor

django/python takes output as ASCII by default, we need to define another (iso-8859) encoding for this piece of code as ¶ is a non-ascii character.

django/python takes output as ASCII by default, we need to define another (iso-8859) encoding for this piece of code as ¶ is a non-ascii character.
@ParvJain
Copy link
Contributor Author

one more thing, now while executing the script this error shows up--

File "/home/trololol/my_proj/src/profiles/admin.py", line 25
SyntaxError: Non-ASCII character '\xc2' in file /home/trololol/edge2/my_proj/src/profiles/admin.py on line 25, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

now it is perfectly working/patched up after i've defined encoding.

@arocks
Copy link
Owner

arocks commented Feb 21, 2015

Thanks Parv! This issue never cropped up in my testing. I have added a commit f90249b to fix this without changing the encoding. Hopefully everything else is working fine as well.

@arocks arocks closed this Feb 21, 2015
@ParvJain
Copy link
Contributor Author

great!

@ParvJain
Copy link
Contributor Author

there is a bit of the problem. with your commit (f90249b), though!
screenshot from 2015-02-21 17 26 17

when i changed it to the commit i've created, it worked flawlessly.

@arocks arocks reopened this Feb 21, 2015
@arocks
Copy link
Owner

arocks commented Feb 21, 2015

Looks like I could have written this a lot better. Firstly using old style % interpolation and not importing unicode literals from future. Please check this commit/branch c46dd40

@arocks
Copy link
Owner

arocks commented Feb 21, 2015

Thank you for bringing this to my attention. I guess I need to do a thorough check of the code for places where I need to insert from __future__ import unicode_literals and remove old style interpolation. I have created an issue #13

@ParvJain
Copy link
Contributor Author

now that's working perfectly!

@ParvJain ParvJain closed this Feb 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants