[sage-devel] Re: Useful methods for graphics objects

this might require some more programming. Éric, what do you think about adding such things to SageManifolds? Could this be feasible? Best, Travis On Tuesday, August 23, 2022 at 4:26:11 PM UTC+9 Kwankyu Lee wrote: > On Monday, August 22, 2022 at 12:04:57 PM UTC+9 Travis Scrimshaw wrote: >

[sage-devel] Re: sage.combinat.integer_vector_weighted.iterator_fast arguments

I thought it produced wrong results when it was for some composition? Perhaps I am mistaken or that was some older version of the code. If the logic is valid for any composition, then we can change the doc. Best, Travis On Monday, August 22, 2022 at 7:59:22 PM UTC+9 axio...@yahoo.de wrote: >

Re: [sage-devel] Graph([(0,'a')]).vertices() raises exception

I think it is a very bad idea to have default sorting based upon hashing. This could make a lot of output appear seemingly random (despite having a natural order), nor there is no way to deal consistently with hash collisions. This would cause far more problems than it would solve when working

[sage-devel] Re: Useful methods for graphics objects

I am not sure how much I support that because there is no metric. If you are working with the Euclidean metric (the usual one you are used to), then you can do sage: l = line3d([(1,2,3), (4,5,6)]) sage: V = RR^3 sage: (V(l.points[1]) - V(l.points[0])).norm() 5.19615242270663 There could also be

Re: [sage-devel] Re: LazyPowerSeriesRing Replacement

I will let Martin discuss the naming as I think the is attached to the name LazyTaylorSeries(Ring). A quick counterpoint to Kwankyu's claim, the power series "is" a function (well, formally), we just usually think of it as being equal to an "easier" function. However, it is meant to be a comple

[sage-devel] LazyPowerSeriesRing Replacement

Hi everyone, Now that https://trac.sagemath.org/ticket/32324 is positively reviewed, I was wondering if there would be any opposition to replacing the current LazyPowerSeriesRing with the next LazyTaylorSeriesRing. This is already happening as the backend for species in https://trac.sagemath

[sage-devel] Re: MSC-2020 -- Class 52: Convex and Discrete Geometry -- CAS Citations from 2000 to 2021

Indeed, it is not only great to see that Sage is increasing in the number of citations* but also the total number of papers citing mathematics software. Best, Travis * In algebraic combinatorics, I sometimes notice that people give an acknowledgement that they have used Sage to help with their

[sage-devel] Re: Proposal: downgrade some packages to experimental

I would like to see the p_group_cohomology fixed. Progress got stalled on that, but I am happy to work on that (while I have time for August). Best, Travis On Sunday, August 7, 2022 at 5:23:46 AM UTC+9 Matthias Koeppe wrote: > The sage_numerical_backends_* packages are on their way out anyway.

[sage-devel] Re: Group algebra bug

I posted on the ticket a long debug of the issue, which comes down to a subtlety with making copies of PermutationGroup_generic and its __dict__. Best, Travis On Sunday, August 7, 2022 at 3:57:59 AM UTC+9 Trevor Karn wrote: > Sorry of course the parent of kH(a) and kH.one() are the same. We do

[sage-devel] Re: Polling for sphinx background style

I slightly protest that one day of voting at the end of the week is not a lot of time for such a consequential vote. That being said, I support grayish (but I also noticed there is so little difference on dark mode). Best, Travis On Saturday, August 6, 2022 at 6:14:54 PM UTC+9 Kwankyu Lee wro

[sage-devel] Re: Docstring Formatting Question: Bullet Points

I don't think we should mandate things so much, but it would be good to have a general policy about this. For example, we have a policy about error messages, but this is not absolute. In particular, this is about breaking ties when an author is doing something that a reviewer dislikes. I don't

[sage-devel] Docstring Formatting Question: Bullet Points

Right now there are two conventions throughout Sage for bullet points (and similar things). Someone has been systematically trying to change everything to one convention (which I am opposed to). However, we as a community have not had a discussion about this as far as I am aware (I believe also

[sage-devel] Re: Implementing Parent with Facade that is not an Element

Hi Trevor, Right...I remember coming across this problem before. Since I know this class is for internal use (simply to index a basis), we can override __call__() instead of _element_constructor_() as we do not need to invoke the coercion framework (and we want this to be fast). This is what

[sage-devel] Re: Finite dimensional algebra generated by matrices

Yes, you have. To better integrate it into Sage, I would expand the existing functionality of FiniteDimensionalAlgebra (and ideally it would do the basis and multiplication table lazily) . This class would likely need some additional work to get it to do what you eventually want, but it would m

[sage-devel] Re: Finite dimensional algebra generated by matrices

One thing you could consider doing is adding an option for the input of the finite dimensional algebra code to take the generators as input and then use that to generate a basis and feed that back into the finite dimensional algebra. I am sure I have written code to compute a basis from a genera

Re: [sage-devel] Question about factories, representations and multiple classes

> > The __classcall_private__() mechanism works well for this kind of > dispatching > > with lots of examples within Sage for this. > > Agreed, and this is fairly standard. However, I am still skeptical about > the > fact this mechanism prevents deep copies... This limits the user's > abili

Re: [sage-devel] Question about factories, representations and multiple classes

> > I'm also relatively new to Sage development, but one thing I can think of > is that you could create a constructor module for your implementation of > Drinfeld module. In short, the way I see it is that you would have a new > module named "constructor" with a class "constructor.FiniteDrinfe

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

croix wrote: > Probably related to https://github.com/sagemath/cypari2/issues/107 ? > > Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit : > > Hi everyone, > > On ticket #30423 <https://trac.sagemath.org/ticket/30423>, Dan, Willie, > > and I h

Re: [sage-devel] Question about factories, representations and multiple classes

For this you want to use __classcall_private__ as otherwise you would likely end up in an infinite loop when you try to construct the subclass. There are lots of examples of this in the Sage library code. Best, Travis On Sunday, May 15, 2022 at 5:42:49 AM UTC+9 Eric Gourgoulhon wrote: > Hi,

[sage-devel] Re: Adding combinatorial divisorial polytopes to sagemath

There are chances, but it depends on many independent factors, such as availability and mathematical expertise. However, before that could be considered, you will need to provide the code first. Best, Travis On Saturday, May 14, 2022 at 7:07:02 AM UTC+9 ie.bat...@gmail.com wrote: > Hi, > > I c

[sage-devel] Re: Finite dimensional algebra generated by matrices

I would advise against having it as an external package if you plan to integrate it into Sage. It further fragments the code and makes it more likely to bitrot from what I have seen. I would instead create a ticket and upload the code to that. Is this a finite dimensional commutative algebra? W

Re: [sage-devel] The SageMath developer map needs your (updated) information

I think I have used a “malformed” email address in the past (which github won’t recognize/accept) with “at” instead of “@“ to try and avoid some spambots, so we might need to change the history in order to fix mine… Best, Travis On Tuesday, May 10, 2022 at 2:11:00 AM UTC+9 Matthias Koeppe wrot

[sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

Hi everyone, On ticket #30423 , Dan, Willie, and I have been working on a parallel-computation based implementation for computing F-matrices that are used in math physics. However, we have been seeing some doctest failures sporadically that involve segf

Re: [sage-devel] orbit decompositions

> > Sorry, I don't know an easy way. I've always just defined them by hand >> whenever needed. >> However, I agree with you that a better way is needed. >> > > I would love for there to be some standard way to define a group action on > a set - preferably maintaining other algebraic properties

[sage-devel] Re: Memory Leak in canonical_label with bliss?

t.will...@gmail.com wrote: > Hi Travis, > I do not know whether the leak is caused within bliss or by sage's wrapper > unfortunately. > But can you reproduce the problem? > Best, > Thomas > > > > On Monday, April 25, 2022 at 2:49:07 AM UTC+2 Travis Scrimshaw wro

[sage-devel] Re: Memory Leak in canonical_label with bliss?

Hi Thomas, Could the memleak be coming from within bliss? Best, Travis On Sunday, April 24, 2022 at 1:50:26 AM UTC+9 t.will...@gmail.com wrote: > Dear all, > > there seems to be a memory leak in canonical_label(...), using bliss. > Here is a test script to demonstrate the problem: > > --

[sage-devel] Re: PowerSeries element class appears in the TAB completion

I don't think such classes were meant to get into the public namespace as they are not so useful (such as promoting a polynomial to a power series). Indeed, as you say, these classes should not be created directly (as they do not have a redirect to pass data to a parent; cf. SemistandardTableau

[sage-devel] Re: Regarding GSoC 2022

Dear Chaitanya, This group is only for questions pertaining to Sage development. Please only post messages concerning GSoC to the sage-gsoc group. Travis On Monday, March 28, 2022 at 1:41:47 PM UTC+9 chaitanya...@gmail.com wrote: > Hello team > > This is Chaitanya Gadgil from Bangalore, Ind

[sage-devel] Re: Using __slots__ in Sage

Hi Trevor, IIRC, yes, and lots. It means you no longer have a __dict__ to work with, which affects @cached_method, pickling, dynamically adding attributes, etc. Not only could using __slots__ in Python classes have far reaching effects within the Sage library, it can affect user's code in the

[sage-devel] Re: SageMath Accepted as GSoC 2022 Mentor Organization

s, 8 de marzo de 2022 a las 5:22:14 UTC+1, Matthias Koeppe > escribió: > >> Wonderful! Thanks for serving as the org admin again this year! >> >> On Monday, March 7, 2022 at 8:03:20 PM UTC-8 Travis Scrimshaw wrote: >> >>> Hi everyone, >>>Great new

[sage-devel] Re: conventions about X.Graded() categories

Hi Vincent, > - how do we specify the grading semi-ring on parents? Right now we only have graded modules (and hence algebras as well), not for (semi-)rings. So for what you want, you might have to implement these categories using the functorial construction (and it would be good to also d

[sage-devel] SageMath Accepted as GSoC 2022 Mentor Organization

Hi everyone, Great news. SageMath has been accepted this year as a mentor organization. I will start the preparations for the next stages. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop re

[sage-devel] Re: Possible bug in SetPartitions constructor?

As Martin said, this is not a bug. However, the error message itself is slightly vague because it only states partition. We could simply run sorted(part, reverse=True) before passing it off to create the Partition in the SetPartitions __classcall__. This would make the behavior less surprising,

[sage-devel] Re: Sage's GSoC Application

Travis Scrimshaw wrote: > Hi everyone, >It is that time of year where we submit an application to Google to be > an organization as part of Google's Summer of Code (GSoC). As I indicated > last year, I will be doing the main administrative work of the submission > and ru

[sage-devel] Re: multicore computing on sage

This is not quite so simple as there are multiple algorithms, some of which use upstream packages, that can be called. Of course, some things could be done by computing each degree in parallel as they are independent. Depending on your setup and what algorithm you are using, you might need to d

[sage-devel] Sage's GSoC Application

Hi everyone, It is that time of year where we submit an application to Google to be an organization as part of Google's Summer of Code (GSoC). As I indicated last year, I will be doing the main administrative work of the submission and running GSoC this year (assuming there are no objections)

Re: [sage-devel] Possible bug: specifying category messes up coercion?

But does the zero element of an algebra (i.e. its neutral element as a > Z-module) really have to refer to the identity element of the algebra? > Also, it probably should throw an error, instead of getting stuck in an > infinite loop. > > Best, > Akos > On Friday, February 4, 2022

Re: [sage-devel] Possible bug: specifying category messes up coercion?

As I stated on the ticket, this is not a bug because you have not properly defined your algebra. It needs to have an (multiplicative) identity specified as it is rightfully expecting it. This is the correct behavior because you are saying it is an algebra without specifying what the algebra str

[sage-devel] Re: making primecount (and its dependency primesieve) standard

+1 On Thursday, November 25, 2021 at 4:32:10 PM UTC+9 Samuel Lelievre wrote: > +1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegr

[sage-devel] Re: Error Building 9.5.beta5 packaging-21.0

er 5, 2021 at 8:30:12 PM UTC-7 Travis Scrimshaw wrote: > >> Hi everyone, >>I am having an issue building packaging-21.0 when upgrading my from >> 9.5.beta2 to 9.5.beta5. It doesn't appear to be something with my setup >> from the log file, but I don't kn

[sage-devel] Re: Error Building 9.5.beta5 packaging-21.0

If possible, I would like to avoid running a make distclean, but that will be my next step if nobody has a better idea. Best, Travis On Saturday, November 6, 2021 at 12:30:12 PM UTC+9 Travis Scrimshaw wrote: > Hi everyone, >I am having an issue building packaging-21.0 when upgrad

Re: [sage-devel] Re: Adèles and idèles

One additional point about including it into Sage (as a sort of counterpoint to Nils' point about discoverability). If it is included, then it will be documented within Sage, which means it will be very likely to appear at the top of Google searches for "SageMath adéles" and we do not (currentl

Re: [sage-devel] Vector spaces with immutable vectors by default

I am -1 on hashability-on-demand for the suggested reason: it could lead to hard-to-track-down bugs in code where we end up calling a hash of something that could be *very* implicit, input to a UniqueRepresentation or a @cached_method/function. As Nils said, the user has no business hashing a m

Re: [sage-devel] Re: Vector spaces with immutable vectors by default

> I think Nils' original solution, of adding an immutable keyword option to > the parent, is a good one. I've run into a similar issue with matrices, > where I had to make them immutable before using them as dictionary keys. > I also ran into this when implementing Lie algebras over matrices.

Re: [sage-devel] printing polynomials with matrix coefficients

For CFM, you can use ascii/unicode_art to improve the printing: sage: M = matrix(2,2,[1,2,3,4]) sage: M [1 2] [3 4] sage: M.set_immutable() sage: CFM = CombinatorialFreeModule(QQ, [M]) sage: CFM.an_element() 2*B[[1 2] [3 4]] sage: ascii_art(CFM.an_element()) 2*B [1 2] [3 4] It would be

[sage-devel] Re: Library code returning int value

Perhaps something towards (2) rather than (5), I believe the general principle is to have any method that a "standard" user will encounter to return a Sage Integer. The reasoning is exactly as you mentioned to avoid surprises to the user (e.g., why does "_.factor()" work for "foo" but not for "

Re: [sage-devel] Bug with subgroup method?

+1 for having the ambient group having a coercion from a subgroup. One other bug is that sage: H.gen(0).parent() is G True sage: H([2]) f^2 sage: _.parent() Multiplicative Abelian subgroup isomorphic to C3 generated by {f^2} Best, Travis On Thursday, June 24, 2021 at 5:24:40 AM UTC+10 David R

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

I don't see why either. I just wanted to check here to see if someone did have an issue before proceeding. Best, Travis On Wednesday, May 26, 2021 at 8:23:02 PM UTC+10 dim...@gmail.com wrote: > On Wed, May 26, 2021 at 8:04 AM 'jonatha...@googlemail.com' via > sage-devel wrote: > > > > Are the

Re: [sage-devel] Re: Minimum Python version to 3.8

. Best, Travis On Friday, May 14, 2021 at 2:06:55 AM UTC+10 dim...@gmail.com wrote: > On Thu, May 13, 2021 at 4:52 PM David Roe wrote: > > > > > > > > On Thu, May 13, 2021 at 6:09 AM Dima Pasechnik wrote: > >> > >> On Thu, May 13, 2021 at 1:34 AM

[sage-devel] Re: Minimum Python version to 3.8

7 support before end of the year. >> >> >> On Monday, May 10, 2021 at 4:12:48 PM UTC-7 Travis Scrimshaw wrote: >> >>> On #30423 <https://trac.sagemath.org/ticket/30423>, which is getting >>> close to completion, we will be using multiprocessing.shared_m

Re: [sage-devel] Minimum Python version to 3.8

Do we have a doctest tag for a minimum python version? Best, Travis On Tuesday, May 11, 2021 at 9:20:00 AM UTC+10 dim...@gmail.com wrote: > On Tue, May 11, 2021 at 12:12 AM 'Travis Scrimshaw' via sage-devel > wrote: > > > > On #30423, which is getting close to

[sage-devel] Minimum Python version to 3.8

On #30423 , which is getting close to completion, we will be using multiprocessing.shared_memory, which is only available on Python 3.8+. However, right now we are at least allowing Python 3.7 (as per the patchbot). So my main proposal would be to bump the

[sage-devel] Re: Proposal: Very short release cycle for Sage 9.4

+1 on this. I know many people who use the latest OSX. Best, Travis On Tuesday, May 11, 2021 at 5:09:55 AM UTC+10 Matthias Koeppe wrote: > ... with a focus on adding support for gcc/gfortran 11 ( > https://trac.sagemath.org/ticket/31786) > and in particular fixing the build on macOS Big Sur wit

[sage-devel] Re: The sign() method in QQbar overlooks some (presumably) easy shortcuts

Hi Ilia, It would be possible to improve the QQbar element sign() method to check the case when they have the same minimum polynomials. See https://trac.sagemath.org/ticket/31767 for a proposal. Best, Travis On Thursday, April 29, 2021 at 9:43:49 PM UTC+10 Ilia wrote: > > Hello everyone, >

[sage-devel] Sage has been accepted for GSoC 2021 as a mentor organization

Students will be able to apply for GSoC from March 30, 2021 - April 14, 2021. For those of you who have posted projects, I will be adding you as a mentor in the next few days. Feel free to add additional projects to the GSoC projects page: https://wiki.sagemath.org/GSoC/2021 Best, Travis --

Re: [sage-devel] Re: Sage GSoC 2021 Projects

ave added a project for expanding Sage's asymptotics module to the >> list which Clemens and I are willing to mentor. >> >> Best wishes, >> Benjamin >> >> Travis Scrimshaw schrieb am Dienstag, 23. Februar 2021 um 00:18:20 UTC+1: >> >>> Hi Clemen

Re: [sage-devel] Re: Sage GSoC 2021 Projects

ies code (in > particular, lazy formal power series)? > > Clemens Heuberger schrieb am Montag, 22. Februar 2021 um 11:35:54 UTC+1: > >> Hi, >> >> Am 22.02.21 um 06:08 schrieb 'Travis Scrimshaw' via sage-devel: >> > Hi everyone, >> > Wi

Re: [sage-devel] Re: Sage GSoC 2021 Projects

Hi Clemens, Google could look at the projects page at anytime now. So it would be good to add them by the end of the week. Best, Travis On Monday, February 22, 2021 at 8:35:54 PM UTC+10 Clemens Heuberger wrote: > Hi, > > Am 22.02.21 um 06:08 schrieb 'Travis Scrimshaw' via

[sage-devel] Re: Sage GSoC 2021 Projects

, 2021 at 1:54:37 PM UTC+10 Travis Scrimshaw wrote: > Hi everyone, >I will be the admin for this year's Sage's GSoC program (for more on > GSoC, see https://summerofcode.withgoogle.com/), taking over after the > amazing job Harald has been doing these past years. This yea

Re: [sage-devel] Cached methods of Cartesian products

This is an issue with the @cached_method, not with these specific methods. The problem comes from the super() call: sage: class Foo: : @cached_method : def check(self, x): : return x : class Bar(Foo): : @cached_method : def check(self, x): :

[sage-devel] Re: Graph Theory Projects in GSoC'21

Dear Akshat, The selection process for organizations for GSoC in 2021 is currently underway. As such, we cannot give any information regarding Sage's participation in GSoC at this time. Any additional queries regarding students/projects for GSoC should be redirected to the sage-gsoc mailing

[sage-devel] Re: root systems and weight lattices, rho and the symmetric_form

Hi Martin, Yes, there is a bug here. The issue comes from the diagonalization: sage: cm = CartanMatrix(['B',3]) sage: cm.is_symmetrizable(True)

[sage-devel] Sage GSoC 2021 Projects

Hi everyone, I will be the admin for this year's Sage's GSoC program (for more on GSoC, see https://summerofcode.withgoogle.com/), taking over after the amazing job Harald has been doing these past years. This year, students will be working on a 175-hour project over 10 weeks; specifically Ju

Re: [sage-devel] Re: [GSoC Mentors Announce] Now Accepting GSoC 2021 Mentoring Organization Applications until Feb 19

aps if we have a mentoring program for new admins, we will be able to >> recruit more admins. >> >> On Wednesday, February 10, 2021 at 12:22:36 AM UTC-8 Travis Scrimshaw >> wrote: >> >>> I think I could probably manage being part of the admin, but I

[sage-devel] Re: [GSoC Mentors Announce] Now Accepting GSoC 2021 Mentoring Organization Applications until Feb 19

I think I could probably manage being part of the admin, but I definitely could not do it alone without someone who knows more about how it works. Best, Travis On Tuesday, February 9, 2021 at 11:46:55 PM UTC+10 David Coudert wrote: > This year is difficult for all of us and we lack motivation

Re: [sage-devel] Re: sorting output dicts in doctests

ders well on documents >> >> R >> >> >> On February 4, 2021 8:34:36 PM GMT-03:00, 'Travis Scrimshaw' via >> sage-devel wrote: >>> >>> Hi John, >>> IIRC, a dict has its keys automatically sorted in the output. >>

[sage-devel] Re: sorting output dicts in doctests

Hi John, IIRC, a dict has its keys automatically sorted in the output. However, if the dict is inside of another object, then no sorting is done. So if it is a simple dict with a total ordering on the keys, then you can simply put the output. You can also run sorted() on the items if they di

[sage-devel] Re: [GSoC Mentors Announce] Now Accepting GSoC 2021 Mentoring Organization Applications until Feb 19

I am happy to mentor, but I am not sure I could take on being an admin this year (next year I could though). Best, Travis On Tuesday, February 2, 2021 at 7:54:01 PM UTC+10 dim...@gmail.com wrote: > Dear all, > > we are looking for projects and mentors for GSoC 2021. > > Myself, I'll pass this

[sage-devel] Re: is_invertible() too slow comparing to rank() over GF(2^k)

It would be good to implement this directly in the Matrix_gf2e_dense class rather than do anything in the generic implementation. However, you have to be a little careful for the case when it is a 0x0 matrix. Best, Travis On Thursday, January 21, 2021 at 5:48:40 AM UTC+10 dmo...@deductivepress

Re: [sage-devel] Re: is ZZ(None) == 0 intentional?

>>> In summary, without even thinking about which approach is better, it's >>> hard to change ZZ(None) without also changing ZZ(0.5), since the >>> argument in both cases is the same: "Python does it that way". >>> However, it seem

[sage-devel] Re: Bug in hom

hink both choices have good reasons. I am not sure > how to collaborate with these issues but I am ready to. Best, Enrique. > > El domingo, 27 de diciembre de 2020 a las 2:49:11 UTC+1, Travis Scrimshaw > escribió: > >> We need to be very careful here about what "same"

[sage-devel] Re: is ZZ(None) == 0 intentional?

Hi Martin, I would think so. It would be natural from a programming perspective as None behaves like False, which is 0 as an integer. None is also the default input for an Integer object. Although somewhat interestingly 0 == None is False. Perhaps someone who has worked more on the integer co

[sage-devel] Re: Bug in hom

ge/local/lib/python3.8/site-packages/sage/modules/matrix_morphism.py > > Type: method > > Best, Enrique. > > > El jueves, 24 de diciembre de 2020 a las 0:41:10 UTC+1, Travis Scrimshaw > escribió: > >> What you're asking for is checking if two matrices defining the

[sage-devel] Re: Bug in hom

What you're asking for is checking if two matrices defining the linear transformations are similar, which involves computing the Smith normal forms of the matrices. This is computationally expensive. Instead, what we do is == becomes a weaker form of equality that is fast (equivalently has stro

[sage-devel] Re: Bug in SpecializationMorphism?

The fact that this behavior is inconsistent is a bug IMO. Judging from the examples and my natural expectation, the QQ example is the behavior we want. Could you open a trac ticket for this? Best, Travis On Friday, December 18, 2020 at 2:44:39 AM UTC+10 Matthias Volk wrote: > Dear all, > > I

Re: [sage-devel] support_order in SubmoduleWithBasis

Submodules need to do linear algebra to compute a basis from the generating set, as well as to pullback vectors into the subspace. The best way that I know of to do linear algebra is to write everything in terms of matrices, and so you need an ordering of your indices. Before, this feature of o

Re: [sage-devel] cocalc and sagemath webpage

First, let me acknowledge my respect and admiration to William for his contributions both to Sage and for having such a great service such as CoCalc. However, I must also disagree with having this being linked with the Sage logo as these are separate entities both in their mission and content.

[sage-devel] Re: "Real Field" -> "Real Floating-point Field"

> > > I would like to discuss the patchbomb at > > https://trac.sagemath.org/ticket/24523 > > The ticket hopes to change the string representation from > "Real Field with XX bits of precision" to "Real Floating-point > field with XX bits of precision". > > +1 -- You received this mes

Re: [sage-devel] Re: Lie subalgebra implementation bug

by step. > > Best, > > Linden > On 22/09/2020 00:22, 'Travis Scrimshaw' via sage-devel wrote: > > Hi Linden, >This works for me in 9.1. So this was either fixed in a later version > or possibly wasn't considered supported in version 8.9 (although probably

[sage-devel] Re: Lie subalgebra implementation bug

Hi Linden, This works for me in 9.1. So this was either fixed in a later version or possibly wasn't considered supported in version 8.9 (although probably the former). So I would recommend upgrading to the latest version of Sage. Side note: if you would like to contribute to Sage, the (semi)s

[sage-devel] Re: Proposal to add "tox" as a standard package - entry point for testing and linting

+1 On Tuesday, September 8, 2020 at 7:18:34 AM UTC+10, Matthias Koeppe wrote: > > tox (https://tox.readthedocs.io/en/latest/) is a popular package that is > used by a large number of Python projects as the standard entry point for > testing and linting. > > Sage 9.1 started to use tox for portab

Re: [sage-devel] Need help in English, French, German, Japanese and Portuguese for 30212

I can do the Japanese version. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on t

Re: [sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.2

I added some comments about unicode art. If someone else wants, this could possibly be expanded to include better unicode support elsewhere in Sage. Best, Travis On Sunday, August 30, 2020 at 5:38:56 AM UTC+10, c.ed...@gmail.com wrote: > > I just noticed 30243 has been closed but not merged yet

Re: [sage-devel] check merge failure on Trac

I normally do $ git checkout -b local_branch develop $ git pull trac branch_on_trac This will add a merge commit, but it will allow you to do the diff and not recompile. Best, Travis On Saturday, August 29, 2020 at 1:51:09 AM UTC+10, Dima Pasechnik wrote: > > On Fri, Aug 28, 2020 at 4:19 PM

[sage-devel] Re: Adding support for discrete differential geometry for SAGE?

epted > 5. Pick new bullet point, goto step 2? > > Thanks a lot, > ~Siddharth > > > On Monday, 20 July 2020 15:05:51 UTC+5:30, Eric Gourgoulhon wrote: >> >> Hi, >> >> Le lundi 20 juillet 2020 01:17:39 UTC+2, Travis Scrimshaw a écrit : >>> >>

[sage-devel] Re: Adding support for discrete differential geometry for SAGE?

Hi Siddharth, That sounds like a good idea. What you will need to do is create a number of tickets to add in the corresponding functionality. Once you have a proposal (which you can ask questions on said tickets), it will be reviewed, where suggestions and comments will be given on possible d

[sage-devel] Re: Feedback needed on Vertex algebra implementation

> > > When writing new modules containing thousands of lines of code, I think it > is important to know that there are more than one way to share this code to > the SageMath Community: > > 1) Post a patch bomb on trac, hoping that people will review it and hoping > the code follows the Sage con

Re: [sage-devel] A issue with the Set function in sage

> >> - the problem is that lists are not hashable, and considered unequal. >> The problem is that in general testing objects for equality is far >> from obvious, might be algorithmically unsolvable, etc. >> >> Why is Set trying then? I can see in the documentation that "Sets with > unhashabl

Re: [sage-devel] Turn off consistent randomness in doctests by default?

On Tuesday, June 23, 2020 at 3:37:59 AM UTC+10, Nils Bruin wrote: > > On Monday, June 22, 2020 at 6:18:11 AM UTC-7, Michael Orlitzky wrote: >> >> Doing so won't consume any extra time >> on any individual machine, and the multitudes of reviewers and patchbots >> running the test on different exa

Re: [sage-devel] Re: Bug in category_singleton.__contains__ or in CombinatorialFreeModule

> > > $ git diff src/sage/sets/disjoint_union_enumerated_sets.py > diff --git a/src/sage/sets/disjoint_union_enumerated_sets.py > b/src/sage/sets/disjoint_union_enumerated_sets.py > index c6d35ea8bd..f5fdba7119 100644 > --- a/src/sage/sets/disjoint_union_enumerated_sets.py > +++ b/src/sage/se

Re: [sage-devel] Re: Bug in category_singleton.__contains__ or in CombinatorialFreeModule

That definitely is not a bug in CombinatorialFreeModule, so there shouldn't be anything changed there. It is doing what it is told: that its indexing set is in finite sets. I would say the bug is purely in the DisjointUnionEnumeratedSets not doing a full check of its member sets. Best, Travis

Re: [sage-devel] Re: Wrong matrix of Permutation

We also recently had a ticket about correcting the permutation action on a matrix, so we also need that to also be consistent. Best, Travis On Tuesday, June 16, 2020 at 4:02:11 AM UTC+10, Nils Bruin wrote: > > On Monday, June 15, 2020 at 10:43:51 AM UTC-7, Nils Bruin wrote: >> >> There's obviou

[sage-devel] Re: Sage 9.1 - Possible bug in how matrices are treated in characteristic 2

I have also posted a fix, Travis On Sunday, June 7, 2020 at 4:49:01 AM UTC+10, Dave Morris wrote: > > Thanks for your detailed report. I confirm that your code crashes sage, > so I opened trac ticket #29181 > to address this issue. > -- You received t

[sage-devel] Re: unicode and pdf documentation build failure

gt; src/sage/docs/conf.py`? There are a lot of unicode characters defined there > already. \DeclareUnicodeCharacter{26AC}{\circ} or something like that? > > > > On Tuesday, June 2, 2020 at 8:24:52 PM UTC-7, Travis Scrimshaw wrote: >> >> Hi everyone, >>I have a patch wi

[sage-devel] unicode and pdf documentation build failure

Hi everyone, I have a patch with some unicode that uses a character (U+26AC, ⚬) that is not recognized by the pdf docbuild. Is there some way I can add an option for the pdf docbuilder to translate this unicode character into a latex symbol so the PDF doc will build? Or is the best option jus

Re: [sage-devel] Re: Proposal: Deprecate all of sage.finance, sage.media, sage.stats in 9.1

It might also be good to also include a message in the deprecation saying if you use this to maybe either a) implement an interface to the library or b) contact sage-devel regarding the desire to keep this feature. Best, Travis On Sunday, May 3, 2020 at 4:29:23 AM UTC+10, Matthias Koeppe wrote

[sage-devel] Re: number_of_partitions returns wrong results under the Windows Subsystem for Linux

I also suspect it comes from some kind of rounding or precision issue, likely in MPFR since nearly all of the computations are done there. At least this is not super pressing since the Bober implementation is not the default implementation, but it is definitely something that should be fixed. B

Re: [sage-devel] Re: Efficient algorithm to express symmetric polynomial in terms of elementary ones

Also, I feel there should be an easy-to-find redirect function in the symmetric function code (IIRC in sfa.py would be the most natural spot), which would tell you to look in the corresponding polynomial code. My natural place to put such checks would be in the polynomial code given that it cou

[sage-devel] Re: Efficient algorithm to express symmetric polynomial in terms of elementary ones

> The bottleneck in `from_polynomial` is the check to test whether the input >> is actually a symmetric polynomial. If you disable the check, the >> computation is moderately fast, although not quite as fast as Vincent's >> code. >> >> Sym.e().from_polynomial(P(seq_taylor), check=False) >> >>

[sage-devel] Re: Efficient algorithm to express symmetric polynomial in terms of elementary ones

hernLib.pdf > > In contrast, doing a similar computation with the same polynomials using > `SymmetricFunctions` takes hours. > > However, I think this is a special case they consider, which makes the > computation probably faster. > > Kind regards > Michael > > Am Die

<    1   2   3   4   5   6   7   8   9   10   >