> Let me sketch my strategy to get closer to the design of other
> distributions. https://trac.sagemath.org/ticket/29865 (waiting for
> review) introduces the two lowest levels - *sagemath-objects*,
> *sagemath-categories.* As soon as we have namespace packages working, the
> latter will
On Wednesday, November 17, 2021 at 10:01:47 PM UTC-8 Kwankyu Lee wrote:
> On Thursday, November 18, 2021 at 11:47:37 AM UTC+9 Matthias Koeppe wrote:
>
>> That would be https://trac.sagemath.org/ticket/29705
>
>
> Yes, all the information could be found in the ticket description and the
>
On Thursday, November 18, 2021 at 11:47:37 AM UTC+9 Matthias Koeppe wrote:
> That would be https://trac.sagemath.org/ticket/29705
Yes, all the information could be found in the ticket description and the
descriptions of the subtickets. But the master plan is buried in the
details. I want to
That would be https://trac.sagemath.org/ticket/29705
Help with documenting the principles and goals of modularization in the
developer's guide is definitely very welcome!
On Wednesday, November 17, 2021 at 6:27:56 PM UTC-8 Kwankyu Lee wrote:
> Hi,
>
> Sage modularization is going on, and I see
Hi,
Sage modularization is going on, and I see in trac many tickets toward the
goal. But I wonder what is the master plan. I mean the plan how sage
library would be split. Here and there I read that some packages in the
sage library will be namespace packages, and others won't be. It would be
Hi all,
I just tagged Flint-2.8.4. This is a critical bug fix release and so
we strongly recommend upgrading.
* Fix a serious bug in fmpz_mod_poly_xgcd for polynomials of large length
* Fix an assertion failure in fmpz_mat_solve_fflu (only relevant if
asserts enabled)
* Fix some bugs on 32
