> On 18/05/2017, at 21:37, Jeroen Demeyer 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 splittin
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?
--
You received t
On 18/05/2017, at 21:24, Jeroen Demeyer wrote:
>
> On 2017-05-18 01:09, François Bissey wrote:
>> And I have a pure
>> python pybrial that install with a minimal setup.py.
>
> If it's pure Python, then how does it access the libBRiAl library?
>
Puzzled me for a while too. It doesn’t.
--
You
On 2017-05-18 01:09, François Bissey wrote:
And I have a pure
python pybrial that install with a minimal setup.py.
If it's pure Python, then how does it access the libBRiAl library?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscrib
Hi all,
Sorry for the cross posting but I believe it is relevant
to sage-devel as a statement of intent.
As you may remember BRiAl is a slightly stripped down
version of polybori that has been autotooled.
I say stripped down because BRiAl do not built the
pypolybori python dynamic library that
