I filed some issues in the thread "ulimit issues and IPython 5.0" in this
list.
El miércoles, 22 de febrero de 2017, 17:23:41 (UTC+1), kcrisman escribió:
>
>
>
>
> Is it possible? It seems to cause problems to sagenb ...
>>
>>>
>>>
> Really? What sort of problems? Just not a new enough version f
it's a bit unfortunate that there is no API provided, only file
input/output.
But yes, why not?
They look like reliable people---something that is important; we had bad
experience with published C code
(for modular decomposition of graphs) that was interfaced with Sage, turned
out to be buggy,
I just checked package content in few minutes...looks interesting (few
dependencies,good manual,code C++...)
+1 with Peleg
--
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
Is it possible? It seems to cause problems to sagenb ...
>
>>
>>
Really? What sort of problems? Just not a new enough version for other
dependencies?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rece
Hi,
We may wish to consider embedding this:
http://algo2.iti.kit.edu/kalp/
into sage, or copying its algorithm.
Peleg.
--
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
On 2017-02-22 11:11, Vincent Delecroix wrote:
>> isinstance would still result in True if the result is a class derived
>> from tuple.
>
> If you are worried about inheritance you can use
>
> sage: type(k) is tuple
Good solution :)
Thanks.
Daniel
--
You received this message because you are s
Le 22/02/2017 à 11:06, Daniel Krenn a écrit :
On 2017-02-22 10:17, Bruno Grenet wrote:
The output line for `type((1,2,3))` is different in Python2.x and
Python3.x: `` versus `tuple`. One solution for your
doctests is to use `isinstance`. Your doctest may become:
```
sage: isinstance(k, tuple)
On 2017-02-22 10:17, Bruno Grenet wrote:
> The output line for `type((1,2,3))` is different in Python2.x and
> Python3.x: `` versus `tuple`. One solution for your
> doctests is to use `isinstance`. Your doctest may become:
>
> ```
> sage: isinstance(k, tuple), isinstance(v, Integer)
> (True, True)
On 2017-02-22 10:30, Clemens Heuberger wrote:
> https://trac.sagemath.org/ticket/22292
Thanks; this ticket tells how to "solve" this.
Daniel
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
Am 2017-02-22 um 10:43 schrieb Daniel Krenn:
> On
> https://trac.sagemath.org/ticket/22398
> the python3-plugin of the patchbot fails in the doctest *output* line
> (, )
> because it includes "". We want to check types there; this
> is the corresponding input line:
> sage: type(k), type(v)
>
The output line for `type((1,2,3))` is different in Python2.x and
Python3.x: `` versus `tuple`. One solution for your
doctests is to use `isinstance`. Your doctest may become:
```
sage: isinstance(k, tuple), isinstance(v, Integer)
(True, True)
```
Best,
Bruno
Le 22/02/2017 à 09:43, Daniel Kre
On
https://trac.sagemath.org/ticket/22398
the python3-plugin of the patchbot fails in the doctest *output* line
(, )
because it includes "". We want to check types there; this
is the corresponding input line:
sage: type(k), type(v)
What to do in this case?
Best
Daniel
--
You received this
12 matches
Mail list logo
