> eval() changes the type from string to tuple. But, to my surprise
> tuple() does not yeild the tuple that is represented by the string but a
> tuple representation of the string.
>
> If eval() does convert correctly why not use it? The string will always
> be a valid tuple.
Hi Vincent,
Altern
Thank you Roel Schroeven
I don't know how I missed the fact that the printDendrogram function
needs tuples not strings.
I didn't recognize that my string was a tuple so I didn't realize
that when I pasted it interactively
in IDEL I was allowing python to change the type.
eval() changes the ty
Roel Schroeven wrote:
>
> You'll have to modify your code so that it creates a tuple instead of a
> string.
It seems that doing it without using a string complicates matters, or at
least increases the line count. I tried it with a list, since you can't
build a tuple on the go since tuples are imm
Vincent Wan wrote:
> Dear all,
>
> I have a simple program that calls a function I got off of active
> state that draws
> a tree given a description of it in standard string form.
>
> My code generates a string description and calls the function to draw
> the tree.
> Instead of drawing the tr
Dear all,
I have a simple program that calls a function I got off of active
state that draws
a tree given a description of it in standard string form.
My code generates a string description and calls the function to draw
the tree.
Instead of drawing the tree it echos the string. But when I ca
