["Followup-To:" nach gmane.comp.mathematics.sage.devel gesetzt.] On 2013-10-21, Nils Bruin <nbr...@sfu.ca> wrote: > The issue is that when Composition gets imported into the global namespace, > the context is lost and you end up with a routine that has a rather > ambiguous name.
+1 > Global namespace is a scarce resource that we have to be careful with, > especially because changes to global namespace are incredibly painful. +1 > I don't see a reason why sage.combinat.composition.Composition needs to be > exposed in the global namespace at all, since it's an element class, not a > parent. +1 -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
