[Cython] 0.20 tests fail with python3.4b2

[Julian Taylor]

hi,

with python3.4b2 numpy_memoryview.acquire_release_cycle fails
looking at the source the test should be disabled, but its still run.

This might be a py3.4 change to doctest, but I know nothing about
doctest, so I wanted to check first if you know something about this.
Interestingly py3.4 runs 64 tests, while python3.3 only runs 32.
the __test__ variable contains the same functions in both python
versions (acquire_release is not in it)

==
FAIL: acquire_release_cycle (numpy_memoryview)
Doctest: numpy_memoryview.acquire_release_cycle
--
Traceback (most recent call last):
  File "/usr/lib/python3.4/doctest.py", line 2187, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for
numpy_memoryview.acquire_release_cycle
  File
"/tmp/buildd/cython-0.20/build/work-dir/memoryview/c/numpy_memoryview/numpy_memoryview.cpython-34m.so",
line unknown line number, in acquire_release_cycle

--
File
"/tmp/buildd/cython-0.20/build/work-dir/memoryview/c/numpy_memoryview/numpy_memoryview.cpython-34m.so",
line ?, in numpy_memoryview.acquire_release_cycle
Failed example:
acquire_release_cycle(a)
Expected:
deallocated!
Got nothing
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] 0.20 tests fail with python3.4b2

[Stefan Behnel]

Julian Taylor, 24.01.2014 22:26:
> with python3.4b2 numpy_memoryview.acquire_release_cycle fails
> looking at the source the test should be disabled, but its still run.

Yes, that's a known problem, the test is fixed in master. In short, Py3.4
has support for finding doctests in the docstrings of C implemented
functions, and thus doesn't need Cython's work-arounds for this anymore.

http://thread.gmane.org/gmane.comp.python.cython.devel/15111

Stefan

___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel