Hi,
Here I withdraw the early premature "giving up" on my recent proposal,
since afterwards there were some positive comments. Hence I open a voting
for
Proposal:
1. Do not use "blocker" label for Issues, as "blocker" means to delay the
release.
2. Instead use "critical" label for a very
Hi,
Here I withdraw the early premature "giving up" on my recent proposal,
since afterwards there were some positive comments. Hence I open a voting
for
Proposal:
1. Do not use "blocker" label for Issues, as "blocker" means to delay the
release.
2. Instead use "critical" label for a very
On Wed, Feb 28, 2024 at 1:01 AM Kwankyu Lee wrote:
> Thank you for making progress on these urgent issues. I suggest the
> following:
>
> 1. Open two other new threads, each of which is for voting on each
> proposal.
> 2. On a proposal, it should be clear that *a positive vote (+1) is for
> the
Thank you for making progress on these urgent issues. I suggest the
following:
1. Open two other new threads, each of which is for voting on each
proposal.
2. On a proposal, it should be clear that *a positive vote (+1) is for the
whole proposal,* and if one is negative to any part of the
Thank you sir.
Yesterday night, I followed instructions from these two sites:
Firstly, I installed miniconda and activated automatically initialization
of conda using this site:
https://deeplearning.lipingyang.org/2018/12/24/install-miniconda-on-centos-7-redhat-7/
.
Then, I installed sage using
On Tuesday 27 February 2024 at 18:09:42 UTC-8 Travis Scrimshaw wrote:
I am not sure it is purely about Python types since it gets changed into C
code.
well ... code dealing with python ints in Py3 needs to deal with
multi-precision PyInt objects, so it can't unwrap these. Whether they are
Dear Sage developers,
The conflicts we've seen in the last several months are multifaceted, but
one of the central issues at hand is how we decide what code is
incorporated into Sage through our review process. I have two goals for
this thread: to describe our current standards (as codified in
Hi Sage developers,
As some of you may be aware, there has been more conflict in the last
several months than normal, including multiple violations of our Code of
Conduct. Sage's mechanism for moderating conflicts and addressing such
violations is a committee, reachable at
On Monday, February 19, 2024 at 1:08:44 PM UTC-8 Matthias Koeppe wrote:
On Monday, February 19, 2024 at 12:46:01 PM UTC-8 Dima Pasechnik wrote:
I don't think the docs describe the interaction between package-version.txt
and install-requires.txt
(and between potential version constraints in
For me, big +1 on (mostly) decoupling (2) from the rest. I think Kwankyu's
suggestion for blockers with positive review being added to all CIs is a
good way to do this. I don't see much utility in doing this at any other
stage.
Best,
Travis
On Tuesday, February 27, 2024 at 3:10:09 PM UTC+9
I am not sure it is purely about Python types since it gets changed into C
code. (For reference, I changed your snippet to cpdef and got the same
result too.) It would be nice if there was an actual specification for
this in Cython. I just get slightly worried after getting translated into C
Blocking on GitHub, I presume, is due to disagreements on a number of topics,
including the topic discussed in this thread. So it's related to the topic, and
personal only as it was done by a person, not by an AI.
On 27 February 2024 22:17:50 GMT, John H Palmieri
wrote:
>That's called
That's normal. In Sage we only maintain one list of packages for the whole
family of distributions (CentOS, CentOS stream, RHEL, Fedora).
Only the newest versions of Fedora have all the packages.
However, likely on your system you will not be able to build Sage.
We test centos-7 only on a
That's called "whataboutism". Invoking what you consider inappropriate
behavior by others is not relevant. Please stay on topic, and please follow
Sage's code of conduct in your posts.
On Tuesday, February 27, 2024 at 1:01:25 PM UTC-8 Dima Pasechnik wrote:
>
>
> On 27 February 2024 20:44:50
On 27 February 2024 20:44:50 GMT, John H Palmieri
wrote:
>Sentences like "At the moment you are actively breaking down the precious
>project fabric, all in the name of you having your way" are personal
>attacks. Please stop.
Blocking on GitHub members of the project is not a personal
On 27 February 2024 20:21:26 GMT, Nils Bruin wrote:
>On Tuesday 27 February 2024 at 10:50:55 UTC-8 John H Palmieri wrote:
>
>
>As Nathan points out, this will likely lead to instability. Someone will
>upgrade some component, and most of the time that will be fine, but
>occasionally it will
If you do that from a terminal, there should be a number of messages
spat back at you before the browser start jupyterlab.
Can you post them?
François
On 28/02/24 09:41, Jan Groenewald wrote:
Hi
sage 10.2 on Debian 12, and
sage -i jupyterlab
sage --notebook=jupyterlab
launches, and the
Sentences like "At the moment you are actively breaking down the precious
project fabric, all in the name of you having your way" are personal
attacks. Please stop.
On Tuesday, February 27, 2024 at 12:36:44 PM UTC-8 Dima Pasechnik wrote:
>
>
> On 27 February 2024 19:37:31 GMT, Matthias Koeppe
Hi
sage 10.2 on Debian 12, and
sage -i jupyterlab
sage --notebook=jupyterlab
launches, and the logo displays and animates, and then stops. I can't get
further. Any ideas?
This was working in sage 10.1.
Regards,
Jan
--
You received this message because you are subscribed to the Google Groups
On 27 February 2024 19:37:31 GMT, Matthias Koeppe
wrote:
>On Tuesday, February 27, 2024 at 10:50:55 AM UTC-8 John H Palmieri wrote:
>
>A pretty safe second choice would be to have "make download" also download
>the relevant files for pip installation and tell pip where to find them. If
>we
On Tuesday 27 February 2024 at 10:50:55 UTC-8 John H Palmieri wrote:
As Nathan points out, this will likely lead to instability. Someone will
upgrade some component, and most of the time that will be fine, but
occasionally it will break something on some platform, and it could be
annoying to
On 27 February 2024 18:50:55 GMT, John H Palmieri
wrote:
>Regarding the proposal to allow standard packages to be pip packages, no
>one really knows how much people rely on the all-in-one tarball that we
>currently distribute. No one really knows how often the "make download"
>option is
On Tuesday, February 27, 2024 at 10:50:55 AM UTC-8 John H Palmieri wrote:
A pretty safe second choice would be to have "make download" also download
the relevant files for pip installation and tell pip where to find them. If
we implemented this second choice [...]
The problem is that such
Regarding the proposal to allow standard packages to be pip packages, no
one really knows how much people rely on the all-in-one tarball that we
currently distribute. No one really knows how often the "make download"
option is used for people who just clone the git repo and want to do all of
On 27 February 2024 17:25:51 GMT, 'Animesh Shree' via sage-devel
wrote:
>This works good if input is square and I also checked on your idea of
>padding zeros for non square matrices.
>I am currently concerned about the permutation matrix and L, U in case of
>padded 0s. Because if we pad
See the documentation:
https://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.linalg.SuperLU.html
As you can see there it computes permutation matrices Pr and Pc and lower
and upper triangular matrices L,U such that
Pr*A*Pc = L*U
so it's not computing a normal LU decomposition of a
Sorry for multiple messages
I just want to say
>sage: p,l,u = a.LU(force=True)
>sage: p
>{'perm_r': [1, 0], 'perm_c': [1, 0]}
It ( {'perm_r': [1, 0], 'perm_c': [1, 0]} ) represents transpose and it
cannot be represented as permutation matrix.
Similar cases may arise for other matrices.
On
For transpose :
In the example we can see permutations are provided as arrays for rows and
cols.
The permutation is equivalent of taking transpose of matrix.
But we cant represent transpose as a permutation matrix.
>>> a = np.matrix([[1,2],[3,5]])
>>> # a * perm = a.T
>>> # perm =
This works good if input is square and I also checked on your idea of
padding zeros for non square matrices.
I am currently concerned about the permutation matrix and L, U in case of
padded 0s. Because if we pad then how will they affect the outputs, so that
we can extract p,l,u for unpadded
On 27 February 2024 15:34:20 GMT, 'Animesh Shree' via sage-devel
wrote:
>I tried scipy which uses superLU. We get the result but there is little bit
>of issue.
>
>
>--For Dense--
>The dense matrix factorization gives this output using permutation matrix
>sage: a = Matrix(RDF, [[1, 0],[2,
I tried scipy which uses superLU. We get the result but there is little bit
of issue.
--For Dense--
The dense matrix factorization gives this output using permutation matrix
sage: a = Matrix(RDF, [[1, 0],[2, 1]], sparse=True)
sage: a
[1.0 0.0]
[2.0 1.0]
sage: p,l,u = a.dense_matrix().LU()
sage:
Dear sir,
Hope you are doing well!
I am trying to follow the instruction to install sagemath in centos7 using
the given commands for centos provided in the link :
https://doc.sagemath.org/html/en/installation/source.html#fedora-redhat-centos-package-installation
But most of the packages are not
32 matches
Mail list logo
