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

Output of python in atom is incorrect, how can I solve this issue? Thanks #1891

Closed
BakhytzhanZZ opened this issue Jun 6, 2019 · 4 comments · Fixed by #2421
Closed

Output of python in atom is incorrect, how can I solve this issue? Thanks #1891

BakhytzhanZZ opened this issue Jun 6, 2019 · 4 comments · Fixed by #2421
Labels

Comments

@BakhytzhanZZ
Copy link

"python" �� ���� ����७��� ��� ���譥�
��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.
[Finished in 0.194s]

@joshisanonymous
Copy link

I came here because I've come across this same issue.

Using Python 3.7, if I do print("troisième") at the console (in PowerShell), the è prints correctly, but running this same code with script in Atom (making sure to use Python 3 instead of 2) returns the question mark for è, even though the character shows up correctly everywhere else in Atom and the encoding for the document is set to UTF-8.

I wouldn't be surprised if this is just a setting issue for script and not a bug at all, but I can't find anything in the settings about encodings or fonts.

@crazytelli
Copy link

I'm having this same problem. print('maçã') gives output "ma��"

@YDum
Copy link

YDum commented Jan 22, 2021

The problem has been discussed in Atom's GitHub, apparently the output in the "console" is in cp1252 in windows, and not in utf-8.
I don't know whether the problem can or should be handled in atom-script, but a solution would be great.

@github-actions
Copy link

🎉 This issue has been resolved in version 3.31.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants