- 26 Jan, 2013 3 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
--HG-- extra : transplant_source : %8A%F1%17%5C%A7%CA%1C%B1%17%A1%C5t%06O%5BI%F2%19Vq
-
- 25 Jan, 2013 1 commit
-
-
Robert Bradshaw authored
Fix error propagation from memoryview-returning functions
-
- 24 Jan, 2013 2 commits
-
-
Matěj Laitl authored
A code like |cdef double[:] foo(): | raise AttributeError('dummy') generated C code like this: | __pyx_L1_error:; | (...) | __pyx_r.memview = NULL; | __Pyx_AddTraceback("view_return_errors.foo", __pyx_clineno, __pyx_lineno, __pyx_filename); | __pyx_L0:; | if (unlikely(!__pyx_r.memview)) { | PyErr_SetString(PyExc_TypeError,"Memoryview return value is not initialized"); | } | __Pyx_RefNannyFinishContext(); | return __pyx_r; |} Which is incorrect in error case, because we set __pyx_r.memview to NULL and then we test it, so that the PyErr_SetString() is always called in the error case, which swallows previously-set error. (it also swallowed the traceback, which I don't understand) A fix is to jump to return_from_error_cleanup label in case return type is memoryview, as it is currently done for the case when buffers are present. A testcase that fauils w/out this fix applied is included, too. v2: fix test under Python 3 by not using StandardError --HG-- extra : transplant_source : G%B5%99Og%D1%81%25k%8F%1F%7B%02V%3E%B9%A4y%FF%EA
-
Matěj Laitl authored
A code like |cdef double[:] foo(): | raise AttributeError('dummy') generated C code like this: | __pyx_L1_error:; | (...) | __pyx_r.memview = NULL; | __Pyx_AddTraceback("view_return_errors.foo", __pyx_clineno, __pyx_lineno, __pyx_filename); | __pyx_L0:; | if (unlikely(!__pyx_r.memview)) { | PyErr_SetString(PyExc_TypeError,"Memoryview return value is not initialized"); | } | __Pyx_RefNannyFinishContext(); | return __pyx_r; |} Which is incorrect in error case, because we set __pyx_r.memview to NULL and then we test it, so that the PyErr_SetString() is always called in the error case, which swallows previously-set error. (it also swallowed the traceback, which I don't understand) A fix is to jump to return_from_error_cleanup label in case return type is memoryview, as it is currently done for the case when buffers are present. A testcase that fauils w/out this fix applied is included, too. v2: fix test under Python 3 by not using StandardError
-
- 22 Jan, 2013 1 commit
-
-
Robert Bradshaw authored
fix indentation error in userguide
-
- 21 Jan, 2013 8 commits
-
-
Lars Buitinck authored
--HG-- extra : transplant_source : %7B%A4%F1%C4/%E4l%2C_%BFF%5B%B7%9C%9F%E0_%2B%15%3D
-
Lars Buitinck authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
- 20 Jan, 2013 6 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
move exception class into shadow function as we may not want to export it under the cython.* namespace at this point
-
- 19 Jan, 2013 4 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
removed broken minivect related code from branch since minivect will not be released as part of 0.18
-
- 18 Jan, 2013 13 commits
-
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Stefan Behnel authored
-
Robert Bradshaw authored
fix import of pyx modules when '' is in sys.path
-
- 16 Jan, 2013 2 commits
-
-
Steinn Steinsen authored
If '' is in sys.path and a module is found the package_path is relative and breaks the build process.
-
Steinn Steinsen authored
If '' is in sys.path and a module is found the package_path is relative and breaks the build process. --HG-- extra : transplant_source : 9%EA%CC%A6%3D%1B9R%EF%0DmM%CFZ%18%F3%EC%06%3B%B7
-