Vincent Delecroix wrote: > On 01/09/16 04:34, Jeroen Demeyer wrote: >> On 2016-08-31 23:26, Vincent Delecroix wrote: >>> Hello, >>> >>> In the optional package giacpy there are some extension classes that >>> depend on SageObject. >> >> Does it really only need SageObject? I see no reason why giacpy would >> need to do that. So the easiest solution seems to make giacpy *not* >> depend on SageObject. > > We should not forbid inheriting from SageObect/Element, > Parent/CategoryObject in external packages. We should just provide a > simple way to automatize the recompilation. This is a step toward > modularization.
Exactly. (See also my other reply.) It would be dumb and totally annoying if all such packages would get rebuilt upon *any* change to the Sage library, and just as bad as having to "manually" figure out /which/ packages might need rebuilding after a change to some specific part of the Sage library. -leif > Moreover, I think that we should fix at some moment a definite API for > all these base classes and coercion. Not now since there is some > cleaning going on at #21380. > > Cheers, > Vincent > -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
