On 6/23/12 6:07 AM, Mike Zabrocki wrote: > here is a "disadvantage" of this solution: > > sage: d = DyckWord([]) > sage: d.maps._parent.maps._parent.maps._parent.maps.map1() > [] > > Its not a bug, its a feature. :) > > > Other thoughts? > > One thing comes to mind that the documentation for .maps or .statistics > should make clear that this is there for organizing the name space for tab > completion. > > I wonder if it should use a novel naming convention like 'maps_.<tab>' > instead of just 'maps.<tab>' That way it is clear that the name space goes > deeper. It seems like a good idea to use some sort > of different naming convention.
Making maps() into an attribute like Mike suggested sounds good to me. I am not so sure about maps_. Isn't it enough if maps?? would give a list of maps and their use cases? Best, Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
