TreeSwift v1.1.35

• Added ability to parse Newick files where a single tree is written across multiple lines

TreeSwift v1.1.34

• Added Tree.num_cherries(), which returns the number of cherries (i.e., internal nodes where all children are leaves) in a Tree
  • Note that, if a Tree is multifurcating, an internal node is only counted as a cherry if all of its children are leaves

TreeSwift v1.1.33

• Fixed bug where Tree.deroot forgot to set the Tree.is_rooted flag to False

TreeSwift v1.1.32

• Fixed Tree.deroot (#20); thanks @balabanmetin and @ekmolloy!

TreeSwift v1.1.31

• Refactored code for small performance gains (#26); thanks @Uzaaft!
• Added support for escaping labels using ' just like in skbio (#27); thanks @valevalorin!
  • Also added support for spaces after commas, e.g. ((D, E)B, (F, G)C)A;

TreeSwift v1.1.30

• Fixed bug in reroot (#24); thanks @smirarab!

TreeSwift v1.1.29

• Added weighted vs. unweighted option to Tree.distances_from_root() and Tree.height()
  • Used to only support weighted distances

TreeSwift v1.1.28

• Fixed bug when writing an output Newick tree that has node/edge params
  • Newick writing seems to now work in all of the following scenarios for any node in the tree:
    • With/without node labels
    • With/without edge lengths
    • With/without node params
    • With/without edge params

TreeSwift v1.1.27

• Added ability to properly load Nexus (or Newick) trees that have both node parameters and edge parameters
  • A given node in the Newick string will look like the following: label[node_params]:[edge_params]edge_length
  • For example: niema[description_about_node]:[description_about_edge]42
    • The node label is niema and is stored in node.label
    • The node parameters are description_about_node and is stored in node.node_params
    • The edge parameters are description_about_edge and is stored in node.edge_params
    • The edge length is 42 and is stored in node.edge_length
  • Thanks @pekarj for the pointers!

TreeSwift v1.1.26

• Fixed bug when loading Nexus files that didn't have spaces around the equal sign on Tree lines
  • Thanks for catching that, @theosanderson!