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
Python 3.3+ support #152
Comments
Taken directly from http://pygments.org/faq/ for version 2.0.2: |
👍 |
1 similar comment
+1 |
Hi, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943257 thank you! |
Closes pygments#152
I have a PR that works for me in #192 . is there anyone here that has access to a windows machine that could help debug the ci failure there? |
@terceiro I don't have access to a windows machine, but I'm guessing this is the problem: Plz try changing that to 3.6 or 3.7 to see if it works. 🤞 UPDATE: Oh nevermind I see you've changed that: https://github.com/tmm1/pygments.rb/pull/192/files#diff-e9f950f17198d3d5e3122a44230a09b9R21 |
The failure has nothing to do with GH-Actions, I also successfully reproduce it locally on Windows 10 + Ruby 2.7 + Python 3.8. I believe the problem is caused by newline character at the beginning of header received from This might be caused by writing |
UPDATE: Yes, my guess was correct. If I replace all So, the problem is: writing I think you want to make sure that Python writes bytes to Ruby. Basically, all instances of |
@slonopotamus Good catch. Indeed there was some mix of unicode and bytes writing in the code: seems to be only some problem in ruby2.2 on mac |
pygments.rb is currently using a development version of pygments 2.0.
Python3.3+ is already supported by the release version of pygments 2.0, which was released on Nov 9, 2014. Please pull latest released verison.
Current release from
vendor/pygments-main/CHANGES
Current latest release version
.
The text was updated successfully, but these errors were encountered: