Activity log for bug #596679

Date Who What changed Old value New value Message
2010-06-20 21:31:44 Eike bug added bug
2010-06-20 21:32:19 Eike freeode: status New Confirmed
2010-06-20 21:32:26 Eike freeode: importance Undecided Wishlist
2010-06-20 21:34:36 Eike description If user defined classes are printed at compile time (with the printc function), their __str__ method is not called. Instead they are rendered as an (ugly in this context) generic ASCII art tree. If user defined classes are printed at compile time (with the printc function), their __str__ method is not called. Instead they are rendered as an (ugly in this context) generic ASCII art tree. Therefore call user defined __str__ method also from printc function. The current behavior is a regression with regards to the old print function!
2010-07-10 16:26:45 Eike tags interpreter
2012-02-29 20:48:36 Eike freeode: importance Wishlist Low
2012-02-29 20:48:36 Eike freeode: status Confirmed In Progress
2012-02-29 20:48:36 Eike freeode: assignee Eike (eike-welk)
2012-02-29 20:48:37 Eike description If user defined classes are printed at compile time (with the printc function), their __str__ method is not called. Instead they are rendered as an (ugly in this context) generic ASCII art tree. Therefore call user defined __str__ method also from printc function. The current behavior is a regression with regards to the old print function! If user defined classes are printed at compile time (with the printc function), their __str__ method is not called. Instead they are rendered as an (ugly in this context) generic ASCII art tree. Therefore call user defined __str__ method also from printc function. Therefore call user defined __str__ method also from printc function. The current behavior is a regression with regards to the old print function!
2012-02-29 21:12:04 Eike freeode: milestone 0.4.2