> On 18/05/2017, at 21:37, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > > On 2017-05-18 11:25, Francois Bissey wrote: >> Puzzled me for a while too. It doesn’t. > > So you are saying that BRiAl consists of two *independent* parts which don't > interact at all? That by itself would increase the reasons for splitting. > Does Sage actually require both parts? >
OK I should elaborate. Polybori used to build a dynamic python library (by that I mean something installed as local/lib/python2.7/polybori/dynamic/PyPolyBoRi.so). And the python interface to polybori/brial first try to import sage. If sage is present, sage’s interface to libbrial is used. If sage is not present it will try load the aforementioned dynamic python library. So at present they do interact, but exclusively through sage. That dynamic python library hasn’t ever been build in any version of brial. It is quite possible to work to restore it or remove all the calling bits. If restoring, it could completely be done python side with libbrial as a dependency. -- 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.
