> On 9/11/2015, at 16:03, Jeroen Demeyer wrote:
>
> On 2015-11-08 15:01, François Bissey wrote:
>> That test now just pass and I have no idea what the new limit is if
>> any. I'll note that it followed by a number of examples that are not
>> tested as they lead to segfault. After the upgrade the
On 2015-11-08 15:01, François Bissey wrote:
That test now just pass and I have no idea what the new limit is if
any. I'll note that it followed by a number of examples that are not
tested as they lead to segfault. After the upgrade they are still
segfaulting. Should I just remove the above doctes
Hi all,
I am working on a series of ticket to upgrade numpy/matplotlib/scipy.
http://trac.sagemath.org/ticket/17642 (numpy)
http://trac.sagemath.org/ticket/19556 (matplotlib)
http://trac.sagemath.org/ticket/17643 (scipy)
The upgrade is developed as being a simultaneous one.
I have a pending ques
On Sat, 7 Nov 2015, Nathann Cohen wrote:
PackageNotFoundError: the package 'my_package' was not found. You
can install it by running 'sage -i my_package' in a shell
About this special case: Interactive loop should catch these and output
some common help text. Maybe even custom
> `js` is certainly not `method`, and certainly not `implementation`.
> Or perhaps `js` is a wrong name all together...
Yeah yeah I agree. I don't mind it being changed at all. Only not into
'algorithm' ;-)
Nathann
--
You received this message because you are subscribed to the Google Groups
"s
On Sunday, 8 November 2015 06:53:26 UTC, Nathann Cohen wrote:
>
> Hello,
>
> > Maybe first thing could be change method -> algorithm? (With
> deprecation, of
> > course.)
>
> With a case-by-case check, however. The replacement you intend seems
> to work on most occurrences, but there is a Gr
Please everyone write Jupyter with "y" when talking
about Project Jupyter and the Jupyter Notebook.
Read "Where does the name come from" at:
https://github.com/jupyter/design/wiki/Jupyter-Logo#where-does-the-name-come-from
: )
--
You received this message because you are subscribed to the Googl
Hi,
Le dimanche 8 novembre 2015 07:32:48 UTC+1, David Roe a écrit :
>
>
>
> I think Nils' point about the downsides of having a cache is one reason
> not to use UniqueRepresentation, both because it can generate references to
> objects you might want to forget, and because sometimes you just wan
