[sage-devel] Re: Renaming/deprecating a class

2012-08-15 Thread Andrew Mathas
OK, so the problem seems to be that I am trying to deprecate an internal class. So, old_class = deprecated_function_alias(123456,new_class) does not work. I also can't use old_class = deprecated_function_alias(123456,sage.combinat.my_module.new_class) inside sage.combinat.my_module as this cr

[sage-devel] Re: simple plotting problem

2012-08-15 Thread Dima Pasechnik
strange fast_float (?) bug: > > On 2012-08-15, P Purkayastha wrote: >> On 08/15/2012 10:58 PM, Dima Pasechnik wrote: >>> On 2012-08-15, P Purkayastha wrote: On 08/15/2012 01:47 PM, Dima Pasechnik wrote: > The following produces a nice plot, all the way down to the horisontal > axis:

[sage-devel] Memory leak in PolyBoRi Ideal

2012-08-15 Thread Timothy Johnson
Hello, I've had some issues recently with PolyBoRi. I'm fairly certain that the code computing an ideal contains a memory leak. Part of my code is as follows. Here T is a data structure storing an nxnxm tensor over GF(2) as a list of nxn matrices, and vec is a vector of length m over GF(2). n, m

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Nils Bruin
On Aug 15, 5:48 am, Simon King wrote: > Anyway, I'd be glad if someone could review #715, #11521, #12313 and > #13370... I'm trying! In the process, I think I might have found a useful debugtool. In sage.structure.coerce_dict, I have added: cpdef refcache(): """ for debug reasons only! A

[sage-devel] Re: Renaming/deprecating a class

2012-08-15 Thread Andrew Mathas
Thanks Simon. Actually, this was the first thing that I tried: SemistandardTableaux_nmu=deprecated_function_alias(9265,SemistandardTableaux_size_evaluation) but it leads to the error: sage: sage.combinat.tableau.SemistandardTableaux_nmu(4,[2,1]) ERROR: An unexpected error occurred while tokenizi

[sage-devel] Re: Renaming/deprecating a class

2012-08-15 Thread Simon King
PS: On 2012-08-15, Simon King wrote: > sage: B = deprecated_function_alias(12345, A) > sage: B() > ...:1: DeprecationWarning: B is deprecated. Please use A instead. > See http://trac.sagemath.org/12345 for details. > #!/usr/bin/env python ><__main__.A instance at 0x449d098> But I guess the cav

[sage-devel] Re: Renaming/deprecating a class

2012-08-15 Thread Simon King
Hi Andrew, On 2012-08-15, Andrew Mathas wrote: > I tried: > > sage: old_class = deprecated_function_alias(123456,new_class.__init__) > > and some variations on this but they all gave the error Classes are callable, and apparently one wants to deprecate the callable. Hence, the following seems to

[sage-devel] Renaming/deprecating a class

2012-08-15 Thread Andrew Mathas
Hi, I want to rename a class, and deprecate the old class name, but it seems that this isn't so easy within the deprecation framework. I tried: sage: old_class = deprecated_function_alias(123456,new_class.__init__) and some variations on this but they all gave the error AttributeError: The na

Re: [sage-devel] Compilation of sage 5.2 fails: Error installing package sagenb-0.9.1

2012-08-15 Thread Stan
Great, thanks, it worked! Could someone change the README.txt from "On recent Debian or Ubuntu systems (in particular Ubuntu 12.04 "Precise"), you need the dpkg-dev package." to "On recent Debian or Ubuntu systems (in particular Ubuntu 12.04 "Precise"), you need the dpkg-dev and libssl-

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Simon King
On 2012-08-15, Simon King wrote: > I have created #13370... ... which now needs review. It fixes one leak that has not be fixed in #715, #12215, #11521 and #12313, and it improves some benchmark for computing echelon forms (which should be interesting, given the original reason for this thread).

Re: [sage-devel] Compilation of sage 5.2 fails: Error installing package sagenb-0.9.1

2012-08-15 Thread Andrea Lazzarotto
2012/8/15 Stan > If it is not a good idea to re-run make in the failed folder and making a > fresh copy of the code files would be better, please let me know. AFAIK that shouldn't cause problems, however you should save a bit of time because of some already compiled files. -- *Andrea Lazzarot

Re: [sage-devel] Compilation of sage 5.2 fails: Error installing package sagenb-0.9.1

2012-08-15 Thread Stan
Thanks for the quick reply, Jeroen! After a long fight with unresolvable dependencies, I finally managed to install libssl-dev and now repeated the make command. Will post later if it worked. If it is not a good idea to re-run make in the failed folder and making a fresh copy of the code files w

[sage-devel] Re: Sage whitespace policy

2012-08-15 Thread Keshav Kini
Robert Bradshaw writes: > On Mon, Aug 13, 2012 at 11:58 PM, Marco Streng wrote: >> 2012/8/14 Robert Bradshaw : >>> Volkers point is right on: the patchbot is purely advisory. >> >> Then I suggest a small change to the patchbot. >> >> iirc, the patchbot (and its blob on trac) shows a huge "plugin

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Simon King
Hi! I have created #13370. My plan is to remove all calls to is_Field(R) and replace them by "R in Fields()". This mainly concerns sage/schemes. Using is_Field will be deprecated. A non-deprecated version will be called _is_Field, and will (still) be used in Fields().__contains__. The important po

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Simon King
PS: On 2012-08-15, Simon King wrote: > Alternatively, one could try to use the category framework in a nasty > way: If "R in Fields()" returns True, then R.category() is refined to a > sub-category of Fields(). In that way, is_Field(R) would only be called > in the first instance of "R in Fields(

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Simon King
Hi Nils, On 2012-08-15, Nils Bruin wrote: > I think I have identified this mysterious object. I think it's > > sage/rings/ring.pyx:1926 > > cdef dict _is_Field_cache = {} > > as introduced in > > http://trac.sagemath.org/sage_trac/ticket/11900 > > with author listed Simon King :-) Oops. > DONT

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Nils Bruin
> #The mysterious object is now L[0] and the next line shows that it > doesn't really have a reference (the only one being the list L which > we have just created) I think I have identified this mysterious object. I think it's sage/rings/ring.pyx:1926 cdef dict _is_Field_cache = {} as introduce

Re: [sage-devel] Compiling Sage 5.2

2012-08-15 Thread Jan Groenewald
Hi Rita, On 14 August 2012 12:07, Rita Morgan wrote: > Thanks for the response. Is it possible to have sage make look at other > locations for these libraries? Instead of looking at /usr/... can they look > at /software/ ... Also, why wont they package these dependencies? Sage is packaged as a

Re: [sage-devel] Compilation of sage 5.2 fails: Error installing package sagenb-0.9.1

2012-08-15 Thread Jeroen Demeyer
On 2012-08-15 09:01, Stan wrote: > Dear all, > > Here is another failure to compile sage 5.2, this time on Ubuntu 12.04, > 64 bit: Error installing package sagenb-0.9.1 You need to install the libssl-dev package on your system. -- -- To post to this group, send an email to sage-devel@googlegro

[sage-devel] Re: Memory leak for matrix operations over QQ

2012-08-15 Thread Simon King
Hi Nils, On 2012-08-15, Nils Bruin wrote: > Interesting data point: The echelonization isn't important. It's the > creation of a non-square matrix space that seems to cement the > integermodring in memory. That is interesting indeed (and surprising to me, because I'd rather expect that the categ

[sage-devel] Compilation of sage 5.2 fails: Error installing package sagenb-0.9.1

2012-08-15 Thread Stan
Dear all, Here is another failure to compile sage 5.2, this time on Ubuntu 12.04, 64 bit: Error installing package sagenb-0.9.1 Below, I pasted the first and last lines of sagenb-0.9.1.log, hope it is helpful: sagenb-0.9.1 Extracting package