|From:||Auto mailings of changes to Lily Issues via Testlilyissues-auto|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5663 Encoding preparations for Python 3.5|
|Date:||Fri, 17 Jan 2020 08:55:18 -0000|
Thanks for testing, this process is incredibly helpful! Unfortunately I can't figure out how to make this work in Python 2 without still needing changes for Python 3 :-( so I guess I'll just put this on my growing list of incompatible changes that need to be added after after running 2to3...
[issues:#5663] Encoding preparations for Python 3.5
Created: Wed Jan 15, 2020 09:42 PM UTC by Jonas Hahnfeld
Last Updated: Fri Jan 17, 2020 08:52 AM UTC
Owner: Jonas Hahnfeld
Encoding preparations for Python 3.5
This is in preparation for Python 3.5 where the default encoding
depends on the value of the LANG environment variable. As far as
I can tell, this was changed later on and at least Python 3.7 and
version 3.8 always default to 'utf-8' on Linux. As I'm proposing to
make Python 3.5 the required minimum, we can't rely on this and need
to force 'utf-8' when reading files that could contain Unicode.
sys.stdout is already in lilylib and codecs.open() always opens
a file in binary mode.
It's not needed anymore as sys.stdout and sys.stderr are wrapped
with encoding writers. (The argument file for show_rules in script
convert-ly is also sys.stdout.)
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|