[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5663 Encoding

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5663 Encoding preparations for Python 3.5
Date: Fri, 17 Jan 2020 08:52:45 -0000

Revert changes for www_post

[issues:#5663] Encoding preparations for Python 3.5

Status: Started
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

  1. Use to decode as utf-8

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.

  1. musicxml2ly: Correct usage of codecs module

sys.stdout is already in lilylib and always opens
a file in binary mode.

  1. lilylib: Remove encoded_write

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 because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Testlilyissues-auto mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]