I am guessing we should something more fundamental in
sage/structure/sage_object.pyx
since we are dealing with SageObject classes.
But I am not sure how to do the
__new__ = object.__new__ in cython.
François
> On 7/12/2016, at 15:25, than...@debian.org wrote:
>
> When setting __new__ = object.
Am Mittwoch, 7. Dezember 2016 01:43:09 UTC schrieb tha...@debian.org:
>
> On 12/07/2016 01:27 AM, François Bissey wrote:
> > On 07/12/16 12:20, tha...@debian.org wrote:
> >> Hi sage-devel,
> >>
> >> we're almost ready to upload Sage to Debian (in fact we basically have
> >> to upload it this
On 12/07/2016 01:27 AM, François Bissey wrote:
> On 07/12/16 12:20, than...@debian.org wrote:
>> Hi sage-devel,
>>
>> we're almost ready to upload Sage to Debian (in fact we basically have
>> to upload it this week to make sure it's included in the next Debian
>> release).
>>
>> However, on Sunday
On 07/12/16 12:20, than...@debian.org wrote:
Hi sage-devel,
we're almost ready to upload Sage to Debian (in fact we basically have
to upload it this week to make sure it's included in the next Debian
release).
However, on Sunday python 2.7.13rc1 was uploaded to Debian and now we
are facing a bu
Hi sage-devel,
we're almost ready to upload Sage to Debian (in fact we basically have to
upload it this week to make sure it's included in the next Debian release).
However, on Sunday python 2.7.13rc1 was uploaded to Debian and now we are
facing a bug that I didn't quite manage to work around y
Frédéric, Peleg is a new contributor to Sage that we met in recent Sage
Days 79. I am sure he can understand the general move toward Python 3 if we
are pedagogical. So thanks for your second reply that appeared while I am
writting this.
I know that you have been working hard on the -> Python 3
The new (python3 or six) range is an iterator. You just have to wrap it
with list( ) to get back to the python2 behaviour if needed.
Le mardi 6 décembre 2016 17:31:20 UTC+1, Frédéric Chapoton a écrit :
>
> DO NOT TOUCH the import of range from six.moves ! This is part of our
> general move towa
Nils Bruin wrote:
> There's a transform that allows you to implement any comparison via a
> key:
[...]
> (of course this all doesn't solve the fundamental difficulty that
> there isn't an ordering that is both total and
> intuitive/mathematically meaningful)
Indeed--and regarding this, I'd be int
DO NOT TOUCH the import of range from six.moves ! This is part of our
general move toward python3 !
And do never use xrange, this is now forbidden.
Frederic
Le mardi 6 décembre 2016 16:26:12 UTC+1, Peleg Michaeli a écrit :
>
> I actually think that this is an unwanted behaviour of `six`.
>
> An
On Monday, December 5, 2016 at 9:15:50 AM UTC-8, Marc Mezzarobba wrote:
>
>
> I'm not sure I follow you: doesn't what cmp() does (if I understand
> right: use the internal order when possible, otherwise sort by type and
> refine by id) do the job? But then, of course, this behavior cannot be
> i
I actually think that this is an unwanted behaviour of `six`.
Anyway, we may let `Graph` handle xrange lists of neighbours if we want to
keep it that way.
On Tuesday, 6 December 2016 17:18:29 UTC+2, Peleg Michaeli wrote:
>
> I have tried to move LollipopGraph into families, but there was a probl
I have tried to move LollipopGraph into families, but there was a problem.
In families, there's the following import:
from six.moves import range
This overrides Python's range. I don't know why. The original
implementation of Lollipop graph uses Python's range, and when it tries to
use the
12 matches
Mail list logo
