An error occurred fetching the project authors.
- 03 Sep, 2007 2 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
- 19 Aug, 2007 4 commits
-
-
Robert Bradshaw authored
avoid argument parsing (via meth_o, meth_noargs) for non-python-object arguments, upgrade version number to 0.9.6.4 compiles and runs SAGE fine
-
Robert Bradshaw authored
previous patch was just for classes
-
Robert Bradshaw authored
-
Robert Bradshaw authored
-
- 29 Jul, 2007 2 commits
-
-
William Stein authored
-
Robert Bradshaw authored
-
- 28 Jul, 2007 2 commits
-
-
William Stein authored
-
William Stein authored
-
- 10 Jul, 2007 2 commits
-
-
Robert Bradshaw authored
For some reason, it actually makes it slower in some of the most common cases (now commented out). Why? It does help in others.
-
Robert Bradshaw authored
-
- 07 Jun, 2007 3 commits
-
-
Robert Bradshaw authored
-
Robert Bradshaw authored
-
Robert Bradshaw authored
-
- 01 Jun, 2007 1 commit
-
-
Robert Bradshaw authored
Now if you inherit cdef methods from another class, you may re-declare the arguments and return variables to be sub-types of the original declared type. This will be especially convenient for the SAGE arithmetic architecture. Type-checking is performed if necessary.
-
- 04 May, 2007 1 commit
-
-
Robert Bradshaw authored
One rarely, if ever, wants the [step] argument to be negative.
-
- 26 Apr, 2007 1 commit
-
-
Robert Bradshaw authored
E.g. for i from 0 <= i < 10 by 2: print i 0 2 4 6 8 Old for-from loops remain exactly the same (using the ++ or --). If step is specified, the increment operator will be += step or -= step, depending on the orientation of the inequalities (as before). NOTE: 'by' is now a keyword
-
- 14 Apr, 2007 1 commit
-
-
Robert Bradshaw authored
The code "__Pyx_GetName(__pyx_b, __pyx_n_[string])" is performed in several thousand places throughout the sage library, and can be quite expensive (a dictionary lookup, possibly raising an error, etc.) This is redundant as the result will always be the same. I perform the lookup once (on loading the module), then have a pointer to the result for all subsequent use. The most common examples are bool/str/int (both as function calls and in isinstance), True/False, and raisign errors. A side feature is that on loading a module with an illegal __builtin__ name, it will complain at load time rather than at run time.
-
- 27 Feb, 2007 1 commit
-
-
Robert Bradshaw authored
"cdef inline foo()" now valid, and will place inline in the resulting c code "cdef o = expr" and "cdef type x = expr" now valid. This may not seem like a huge change, but it ended up requiring quite a bit of work. The variables are still all declared at the top, but the assignment takes place at the specified line in the code. If an assignment is made at declaration, the variable is initalized to 0 rather than None (also skipping an INCREF) and Py_XDECREF is used on exiting the function (in case an error occured before the actual value was calculated). Hence these variables MUST NOT be used before they are defined or it will probably segfault.
-
- 27 Jan, 2007 1 commit
-
-
Robert Bradshaw authored
De-allocate function temp variables _after_ computing return value, in case an exception is thrown, caught, and said temp variables still need to be accessed.
-
- 16 Jan, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 10 Jan, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 18 Dec, 2006 2 commits
-
-
William Stein authored
I recently ran into this problem myself (as the current code causes Python to crash), so I whipped up a quick patch that fixes it for me. I think it follows all of the weakref guidelines now. The patch is against the LXML svn pyrex (http://codespeak.net/svn/lxml/pyrex/). Is there a different SVN I should be pointing to? It patches functions generate_new_function, generate_dealloc_function, generate_traverse_function, and generate_clear_function. The patch just compares the entry.name against "__weakref__"; this could probably be centralized in the Entry object if so desired.
-
William Stein authored
Apply Nick Alexander's patch so that Sagex that embeds positions in module, cdef class, and def class docstrings.
-
- 03 Nov, 2006 1 commit
-
-
William Stein authored
-
- 25 Oct, 2006 1 commit
-
-
William Stein authored
-p, --embed-positions If specified, the positions in Pyrex files of each function definition is embedded in its docstring. This is very useful to support interactive viewing of *Pyrex* source code in, e.g, IPython.
-
- 23 Oct, 2006 1 commit
-
-
William Stein authored
-
- 22 Oct, 2006 1 commit
-
-
William Stein authored
This required a number of changes to a few files. Basically, the full module name is determined in Main.py. It is then passed around a bit until it is used when generating tp_name. This change was needed because otherwise pickling of extension classes with full module names like sage.rings.integer.Integer would fail (since Python would look for integer.Integer instead). NOTE: This is pickling of the extension class itself, not of instances (which could also fail, because the class doesn't pickle).
-
- 20 Oct, 2006 2 commits
-
-
William Stein authored
-
William Stein authored
-