Over the years, it has been suggested that our project seek affiliation
with the NumFocus organization (https://numfocus.org/)
*2016:* E.M. Bray asks in
https://groups.google.com/g/sage-devel/c/8-BfX8KxFuI/m/CQRmz_3vDQAJ: Is
there any particular objection about approaching NumFOCUS [...]?
Another proposed change: https://github.com/sagemath/sage/pull/37054 ("Do
not send people to sage-flame")
On Saturday, December 9, 2023 at 11:54:05 AM UTC-8 Matthias Koeppe wrote:
> As suggested in the thread "Policy for disputed PRs: discussion" (
>
I have done more digging. If I am not mistaken, what governs the coercion
is the function `pushout` in `categories/pushout.py`. For each
construction functor there is a hardcoded rank, such as 9.5 for the
InfinitePolynomialFunctor, 10 for the MatrixFunctor, or 9 for the
PolynomialFunctor and
Hi Volker, William,
On Wednesday, January 10, 2024 at 6:50:10 AM UTC-8 William Stein wrote:
1. There are over 20 pull requests labeled as "disputed" [1]. To
resolve these pull requests, we will be appointing an editor with no
direct involvement in the pull request to make a judgement call on
> I don't think it's off-topic to once again point out that this way of
phrasing it is very developer-centric. That's not a wrong way to look at
it, but an end-user-centric way of looking at it is also valid.
It seems to me that "developer" here refers to a very different kind of
On Sat, 2024-01-13 at 14:54 +0530, Niranjana K M wrote:
>
> I thought the installation would replace the previous builds when new
> system packages are available. It is preferring old local spkg installs, if
> already present, than new versions in system. But if it is spkg only it is
> going for
OK, possibly I now understand Matthias Köppe's comment on the PR. He said
that the pushout of R and S looks suspicious (this is indeed computed in
ModuleAction.__init__ and seems to govern the process):
sage: R
Univariate Polynomial Ring in z over Rational Field
sage: S
Univariate Polynomial
I find the MatrixSpace example interesting:
sage: R = MatrixSpace(QQ, 1)
sage: P = PolynomialRing(R, names="z")
sage: Q = PolynomialRing(QQ, names="z")
sage: Q.gen() * P.gen()
[z]*z
sage: P.gen() * Q.gen()
[z]*z
sage: coercion_model.analyse(P.gen(), Q.gen(), operator.mul)
(['Action discovered.',
Thank you Michael Orlitzky, it worked after cleaning the previous builds. I
did,
$ make maintainer-clean
Which is equivalent to, according to the Makefile,
$ make distclean bootstrap-clean
I thought the installation would replace the previous builds when new
system packages are available. It is
How can I find out what causes this? How can I find out where this action
is defined?
I played around a little, but without any insights. It seems that most of
the time, the coercion tries to do the embedding in the base ring, but not
always. The MatrixSpace seems to be another exception.
10 matches
Mail list logo
