[sage-devel] Re: random_element and randtest_element

Wed 2018-06-06 01:09:27 UTC, Kwankyu Lee: > > Vincent Delecroix: >> >> What do you think? Does the name randtest_element look ok? > > How about "_random_test_element", as this method needs > not to be revealed to users, unlike "random_element" and > "some_elements". This is better than what I

Re: [sage-devel] Re: Severe regression in construction of matrices

On 2018-06-06 02:51, Travis Scrimshaw wrote: Multiple inheritance Cython allows multiple inheritance (in limited ways), so that's not the issue. UniqueRepresentation This is the *real* issue. As far as I know, this doesn't work for Cython classes. -- You received this message because

Re: [sage-devel] Re: Severe regression in construction of matrices

On 2018-06-06 00:39, Nils Bruin wrote: Would it be a problem to splice in a cdef class somewhere that provides cdef attributes for _nrows and _ncols and then provides python-level methods to access these values from python? One thing which could work is to create an abstract base class for

[sage-devel] Re: Suggestion for the SageMath website

On Wednesday, 6 June 2018 16:36:44 UTC+2, Vincent Klein wrote: > > Another alternative is to display all the packages in a slow scrolling > horizontal list ScrollingPackagePrototype.html > > . > Im not sure

[sage-devel] Re: Suggestion for the SageMath website

Another alternative is to display all the packages in a slow scrolling horizontal list ScrollingPackagePrototype.html . Im not sure if the move is too disturbing for the reader or not. Le vendredi 1 juin

[sage-devel] Patching policy

I have recently re-written the nixpkgs sage package to use system packages[1] (not merged yet). While doing that I noticed that while sage patches a lot of its dependencies (81 out of 276 packages have a `patches` folder). There are more or less 3 categories of patches: 1.

[sage-devel] Re: Suggestion for the SageMath website

I just mean so it appears below the part visible in standard desktop browsers, i.e. so it is not the first thing you see when you load the page. "Below the fold" is my terminology for something that requires an action to read it, such as was required on this ancient IBM ThinkPad:

Re: [sage-devel] random_element and randtest_element

I agree with Thierry and also Jeroen: If there are corner cases, you should just test them all outright in a TESTS section and/or via some_elements() and/or passing them explicitly as TestSuite(foo).run(elements=bar). Heisenfailures are very difficult to debug: One run, doctests fail. You make

[sage-devel] Re: Suggestion for the SageMath website

Le mercredi 6 juin 2018 17:06:45 UTC+2, Bill Hart a écrit : > > I would personally put it on the lower part of the page, so that it is > "below the fold" on most browsers (due to its scrolly nature). But maybe > others prefer it higher up. > "below the fold", you man under library and search

[sage-devel] Re: Suggestion for the SageMath website

Le mercredi 6 juin 2018 17:06:45 UTC+2, Bill Hart a écrit : > > I would personally put it on the lower part of the page, so that it is > "below the fold" on most browsers (due to its scrolly nature). But maybe > others prefer it higher up. > "below the fold", you mean under library and search