Sorry if this is answered somewhere in the new documentation, I couldn't
find it: What is the intended procedure for migrated issues which were in
"needs review" state and already had a branch? Am I to push the branch to
my own fork and create a fresh pull request for each such issue?
--
You re
I usually just run "make build" instead of "make" to skip building the
documentation (with unmodified ./configure arguments). Does that satisfy
your needs?
Best,
Lorenz
On Thu, 16 Mar 2023 11:00:08 +0100, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Dear all,
>
> I would like to co
How about .linearize()?
(I think this method should also optionally take a list
of monomials as an argument, since there are situations
in which users would like to force their own ordering.
Returning the same monomial vector again would then of
course be redundant, so in that case the method co
Back in the days of trac, we sometimes had meta tickets that anyone
could edit, for things such as wishlists or keeping track of larger
projects. Some of these meta tickets were turned into GitHub issues,
but now they are no longer editable by anyone except the original
author (or so it seems). I
Sage Days 123 in Leuven ended yesterday and quite a few pull requests
have come out of it already, most of them from new contributors. 🎉
I would like to encourage potential reviewers to have a look at them
sooner rather than later in order to hopefully keep some of the fresh
momentum alive. (Plea
