[sage-devel] Re: 10 year anniversary of Sage

10 years.. not much for a CAS project I guess. All the more impressive how far this project came in this time. Thank you for this nice piece of software!! :) Best regards, Patrick -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

Ok, command line tools updated. (Side note: reinstalling via xcode-select didn't seem to be an option. I downloaded and installed a the most current version from Apple's developer site.) What now? I tried make distclean make but I'm still getting the same error. Let me just say thanks again

Re: [sage-devel] Re: set or dict ?

On Saturday, February 7, 2015 at 10:47:32 AM UTC-8, vdelecroix wrote: > > Let me answer again: this is perfectly consistent. Set and dict use > the same datastructure and both have similar performance with respect > to membership test. > Yes, indeed. Thanks for pointing that out! I wasn't able

Re: [sage-devel] Re: set or dict ?

Let me answer again: this is perfectly consistent. Set and dict use the same datastructure and both have similar performance with respect to membership test. sage: d = dict() sage: s = set() sage: for i in range(1, 11): : for z in Combinations(range(2*i), i): : t = frozenset(z)

[sage-devel] Re: set or dict ?

On Saturday, February 7, 2015 at 7:02:33 AM UTC-8, Nathann Cohen wrote: > > Does that make any sense to you ? > Possibly. dicts get used a lot in python and sets less so. So some optimization might have happened to dicts that wasn't followed through on for dicts. The time you're trying to measur

Re: [sage-devel] Re: set or dict ?

Hi, Le 07/02/2015 16:50, mmarco a écrit : AFAIK, internally sets are implemented just as dictionaries with no values. So it wouldn't really make sense lookup to be faster in a dictionary than a set. Indeed sets in python also want hashables... I must have confused with another language :-/

Re: [sage-devel] set or dict ?

There is the Sage Set type which wraps Python's frozenset. Nathan did not say whether the comparison was with that or Python set and it may well make a difference. John On 7 February 2015 at 15:51, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > 2015-02-07 16:30 UTC+01:00, Julien Puydt :

Re: [sage-devel] set or dict ?

2015-02-07 16:30 UTC+01:00, Julien Puydt : > Le 07/02/2015 16:02, Nathann Cohen a écrit : >> Hello everybody ! >> >> In #17712, David defines a set S and frequently calls 'x in S'. He ran >> some tests and which seem to say that it is actually more efficient to >> implement this set as a dictionary

[sage-devel] Re: set or dict ?

AFAIK, internally sets are implemented just as dictionaries with no values. So it wouldn't really make sense lookup to be faster in a dictionary than a set. Lookup time might deppend strongly on the order in which the dictionary/set is constructed, and on the existence of hash collissions. I r

Re: [sage-devel] set or dict ?

Le 07/02/2015 16:02, Nathann Cohen a écrit : Hello everybody ! In #17712, David defines a set S and frequently calls 'x in S'. He ran some tests and which seem to say that it is actually more efficient to implement this set as a dictionary associating 'True' (or anything else) to its keys...

[sage-devel] Re: Integrate sage into spyder

I thinki it would be good to have some kind of IDE to work on sage development. I would like to add a request though: having some integration with the pdb debugger (sage has a wrapper for that through the "trace" command). I have writen some simple qt app to serve as a front end for step-by-ste

[sage-devel] set or dict ?

Hello everybody ! In #17712, David defines a set S and frequently calls 'x in S'. He ran some tests and which seem to say that it is actually more efficient to implement this set as a dictionary associating 'True' (or anything else) to its keys... http://trac.sagemath.org/ticket/17712#comment:16

[sage-devel] Re: Citing the same paper in docstrings of two different methods

Clemens Heuberger wrote: > Are there other options? What are your recommendations? Assuming the two modules are part of the same package, I would add a separate REFERENCES section somewhere in the package and make both docstrings point to that section. -- Marc -- You received this message be

Re: [sage-devel] Citing the same paper in docstrings of two different methods

> - remove the "REFERENCES: ..." part in one of the modules and live with the > fact that there is a hyperlink from one module to the other. +1 Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop rece

[sage-devel] Citing the same paper in docstrings of two different methods

I'd like to cite the same paper in the docstring of two different methods in different modules. So ALGORITHM: See [HKP2015]_, Section 6. REFERENCES: .. [HKP2015] ... , :arxiv:`1502.01412`. in one module and ALGORITHM: See [HKP2015]_, Section 4

Re: [sage-devel] Sagemath : wild experiments

On 2015-02-06 20:32, Julien Puydt wrote: I reported a wishlist bug on pari's debian package (#77237). That should be #777237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777237 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscrib

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

Looks like a toolchain problem. Can you try reinstalling the OSX compiler command line tools? (xcode-select --install) On Saturday, February 7, 2015 at 4:42:49 AM UTC+1, Xander Faber wrote: > > Hi Bill, > > Thanks for the detailed instructions. mpir-2.7.0 and mpfr-3.1.2 build > fine on my sys

[sage-devel] Integrate sage into spyder

I hadn't heard of spyder before Vincent mentioned it so I looked into it and it seemed quite impressing. It runs on all platforms (including Windows), supports both Python 2.7 and 3 and is actively being developed. Spyder is quite modular in that every par