[sage-devel] Re: Manifold equality and UniqueRepresentation

On Wednesday, November 4, 2015 at 2:10:51 PM UTC-8, Eric Gourgoulhon wrote: > > Hi sage-dev, > > There is an ongoing discussion at #18529 > about defining __eq__ for > manifolds and whether one should > use UniqueRepresentation (which implements equality by

[sage-devel] Re: Various issues with LaurentPolynomialRing

Hey Salvatore, first of all thank you for your answer, it looks like you are one of the > person I pester the most with these issues. > I think I'm the one who knows the most about this because I have made the most recent additions and fixes to that part of Sage (although I'm happy to be wron

[sage-devel] Re: Manifold equality and UniqueRepresentation

I should note for those not wanting to read through the discussion in full that we arrived at the current design dealing with the following issues: - We need the manifold to be defined in order for check the charts (as it is the domain of said map). - We can't just use EqualityById without Uniqu

[sage-devel] Manifold equality and UniqueRepresentation

Hi sage-dev, There is an ongoing discussion at #18529 about defining __eq__ for manifolds and whether one should use UniqueRepresentation (which implements equality by id). If anybody has any opinion on this, she/he is welcome to join the discussion. T

Re: [sage-devel] source code comments: doctesting instructions

On Wed, 4 Nov 2015, William Stein wrote: Does this mean computers aren't constantly getting faster anymore? l miss the 90s... :-) # long time - 90bogoseconds ? -- Jori Mäntysalo

Re: [sage-devel] source code comments: doctesting instructions

On 2015-11-04 16:08, William Stein wrote: Does this mean computers aren't constantly getting faster anymore? I think you have a point. They do get more cores and more SIMD parallelization though. -- You received this message because you are subscribed to the Google Groups "sage-devel" group

Re: [sage-devel] source code comments: doctesting instructions

Does this mean computers aren't constantly getting faster anymore? l miss the 90s... :-) On Wednesday, November 4, 2015, kcrisman wrote: > >> That's actually a great idea! >> >> Although, to simplify parsing, I would only allow seconds with a syntax >> similar to optional: >> >> # long time: 300

Re: [sage-devel] source code comments: doctesting instructions

+1 On 4 November 2015 at 13:55, kcrisman wrote: >> >> That's actually a great idea! >> >> Although, to simplify parsing, I would only allow seconds with a syntax >> similar to optional: >> >> # long time: 300s >> > > Good resolution, very nice. > > -- > You received this message because you are s

Re: [sage-devel] source code comments: doctesting instructions

> > > That's actually a great idea! > > Although, to simplify parsing, I would only allow seconds with a syntax > similar to optional: > > # long time: 300s > > Good resolution, very nice. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To u

Re: [sage-devel] source code comments: doctesting instructions

On 04/11/15 09:39, Jeroen Demeyer wrote: On 2015-11-04 12:19, Vincent Delecroix wrote: One solution with long doctest is to (optionally) flag them with a time indication # long 30sec # long 1min # long 1hour # long 3year That's actually a great idea! Although, to simplify parsing, I

Re: [sage-devel] source code comments: doctesting instructions

On 2015-11-04 12:19, Vincent Delecroix wrote: One solution with long doctest is to (optionally) flag them with a time indication # long 30sec # long 1min # long 1hour # long 3year That's actually a great idea! Although, to simplify parsing, I would only allow seconds with a syntax si

[sage-devel] Re: Various issues with LaurentPolynomialRing

Hi Travis, first of all thank you for your answer, it looks like you are one of the person I pester the most with these issues. TropicalSemiring is, unfortunately, not what I am looking for. The object I need is a multiplicative abelian group on generators n generators y_i and an addition \prod y

Re: [sage-devel] source code comments: doctesting instructions

One solution with long doctest is to (optionally) flag them with a time indication # long 30sec # long 1min # long 1hour # long 3year Then, when testing we could add an option to skip the one which are too long for our purpose sage -t --all --skip-longer-than 2min And I think that the d

Re: [sage-devel] Whether sage have a library of triangle groups?

Please, post this kind of questions: - either on the forum ask.sagemath.org - or on the mailing list sage-supp...@googlegroups.com The mailing list sage-devel is dedicated to sage *development*. On 04/11/15 04:12, akhilesh p wrote: Whether sage have a library of triangle groups? -- You rece

Re: [sage-devel] Re: ipython-notebook: show picture in notebook (e.g. latex-tikz)

On Wednesday, 4 November 2015 08:27:51 UTC, Jean-Baptiste Priez wrote: > > Thanks William. > > For what it's worth, >> >> view(transducers.GrayCode()) and show(transducers.GrayCode()) >> >> just work also in SageMathCloud -- example: >> >> >> https://cloud.sagemath.com/projects/4a5f0542-5873-4

Re: [sage-devel] Sage on OS X: El Capitan

On Tue, Nov 3, 2015 at 10:33 PM, Stefan wrote: > Discussion in the hallway with a colleague the other day (paraphrased): > > Colleague: "So, is Sage working yet on the latest OS X?" > Me: "Mixed signals. People get errors, it seems to work if you enable root > again" > Colleague: "Oh no, I don't w

[sage-devel] Whether sage have a library of triangle groups?

Whether sage have a library of triangle groups? -- 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 post to this group, sen

Re: [sage-devel] Re: ipython-notebook: show picture in notebook (e.g. latex-tikz)

Thanks William. For what it's worth, > > view(transducers.GrayCode()) and show(transducers.GrayCode()) > > just work also in SageMathCloud -- example: > > > https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2015-11-03-212108-tikz.sagews > > I finally added t