-
Notifications
You must be signed in to change notification settings - Fork 188
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
Unicode, e.g. crescent moon 🌙 & beers 🍻 breaks under Python 3 #159
base: master
Are you sure you want to change the base?
Conversation
Seems to only affect pyenv-installed Python 3.4; Python 2.6 and 2.7 are fine in my tox.
@peterbe Now I get what you mean by feels like an environment issue. On my OSX El Capitan dev machine:
The part I don't yet understand is the staging environment which triggered all this is an Ubuntu box... |
Sorry I haven't had time to review. Still on my todo list. |
To see if it's reproducible on Travis which if true may make whatever the underlying issue(s) are easier to debug. https://docs.travis-ci.com/user/multi-os/
To see if only Python 3.5 fails at the building environment under OSX stage and we can perhaps get 3.3 or 3.4 out. However this is not very inspiring... apache/libcloud@95338d8
@peterbe No worries, it looks to be OSX-specific at this point. I was able to reproduce the test failure in this PR on a different OSX El Capitan box but not on an Ubuntu 14.04 LTS box suggesting it is OSX-specific, or at least under OSX building The original original issue which triggered this appears to be a completely different Django issue with the console backend, which explains why it failed on the staging environment but emails with 🌙 🍻 in production are sending without issue.
From Sentry, formatted for readability:
|
I'm trying to wrap my head around what's going on. I checked out your branch and verified that all is well, under python 2.7. By the way, I have OSX too.
Cool. Then I created a fresh virtualenv based on Python 3.5. It installed:
Yeah, there it gets weird:
So, are you saying that this error NOT happen if you run Python 3 on Linux? So the problem only manifests itself on OSX, in Python 3x? Is that right? |
Another thing I don't understand is that, this works on the master branch:
|
Did anyone ever work out what's going on here? I've encountered this after moving to a new laptop, both old and new laptops are both running the newest MacOS and all the same library versions (installed with Poetry so there's a lock file). I found that passing through UTF-8 encoded bytes to |
So it's still a bug after 6 years of Python and |
Well, I guess GitHub Actions just runs |
As suggested by @peterbe on #157, please see for more details.
Not sure how to proceed so if anyone can make the test pass, go for it and good on you 👍