On Monday, July 05, 2010, Adolfo Gonzalez wrote: > Any idea if this bug is going to be fixed?
I reported the same problem earlier but there was no interest from the Agilo developers to address the issue. I think it is just very bad software development to extend the API of a model and then rely on the incompatible changes. The Adapter pattern which addresses such problems has been around for a very long time and even has a really good Python implementation (zope.interface and optionally zope.component). Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
