On Sunday, March 4, 2018 at 10:58:32 AM UTC, Eric Gourgoulhon wrote: > > > I'm also -1 for this, after the argument given by Travis on the ticket: > injecting silently names in the global namespace may override names already > defined by the user. Initially, I naively thought this was a good way to > avoid cluttering the global namespace of a generic Sage session. >
It's actually worse than that: At runtime, it's not even clear if there a unique "global" namespace, so (apart from the fact that clobbering a namespace is a bad idea), you'd even have a hard time getting a hold of the appropriate namespace to clobber. I'd subscribe to the advice of guiding your users to use "from sage.manifolds.operators import *" or something similar. Defining a function to do this is tricky for the reason mentioned above (and getting access to the function would require an import anyway). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
