An error occurred fetching the project authors.
- 23 Sep, 2007 1 commit
-
-
Stefan Behnel authored
-
- 11 Sep, 2007 2 commits
-
-
Stefan Behnel authored
use 'with GIL' instead of 'withGIL' to avoid introducing a non-Python keyword and to support later extension for other contexts
-
Stefan Behnel authored
use 'with GIL' instead of 'withGIL' to avoid introducing a non-Python keyword and to support later extension for other contexts
-
- 10 Sep, 2007 2 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
- 01 Aug, 2007 1 commit
-
-
Stefan Behnel authored
-
- 29 Jul, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 07 Jul, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 07 Jun, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 26 Apr, 2007 2 commits
-
-
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
-
Robert Bradshaw authored
Added a bint c type, which is a c int that coerces to and from python objects via the boolean routines. The purpose of this type is to free the coder from having to use bool() when retrieving and returning semantically "boolean" values (e.g. the result of a compare). The bint type is a subclass of the int type, and the only difference is that it uses PyBool_FromLong and PyObject_IsTrue rather than PyInt_FromLong and PyInt_AsLong. Arithmatic on bints will return ints. Where it makes sense, several builtin functions have been re-declared to return bints, as well as comparisons and the boolean operations or, and, and not.
-
- 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.
-
- 24 Feb, 2007 1 commit
-
-
Robert Bradshaw authored
-
- 23 Feb, 2007 1 commit
-
-
Robert Bradshaw authored
Changes in grammar required change for this, see http://www.python.org/dev/peps/pep-0308/ Most noteably for list comprehensions (dissambiguate the if)
-
- 16 Jan, 2007 2 commits
-
-
Robert Bradshaw authored
-
Robert Bradshaw authored
-
- 10 Jan, 2007 1 commit
-
-
Robert Bradshaw 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
-