LilyIssues / Issues / #5633 musicxml: Replace new module by type() builtin

Anonymous - 2019-12-10

Description has changed:

Diff:

Needs: -->

Patch: new --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-12-10

Passes make, make check and a full make doc.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-12-13

Patch: review --> countdown
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-12-13

Patch on couuntdown for Dec 15th.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-12-15

Patch: countdown --> push
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-12-15

Patch counted down - please push

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jonas Hahnfeld - 2019-12-15

labels: --> Fixed_2_21_0

status: Started --> Fixed

Patch: push -->
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pushed to staging as

commit a1494ab840c38ee71decf62d3e924d54d29c91fc
Author: Jonas Hahnfeld <hahnjo@hahnjo.de>
Date:   Mon Dec 9 20:12:50 2019 +0100

    Issue 5633: musicxml: Replace new module by type() builtin

    The new module has been deprecated in Python 2.6 and removed in
    version 3.0. The type() builtin is available since Python 2.2 but
    it requires new-style bases, so make Xml_node inherit from object.

musicxml: Replace new module by type() builtin

Issue Tracker for LilyPond

Searches

Help

#5633 musicxml: Replace new module by type() builtin

Discussion