Re: [Cython] Cython 0.14.1 release candidate
On Fri, Jan 28, 2011 at 9:39 PM, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 29.01.2011 01:55: On Fri, Jan 28, 2011 at 3:38 PM, Dominic Sacré wrote: On Fri, Jan 28, 2011 at 11:40 AM, Robert Bradshaw wrote: New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz Is it just me, or do the release candidates break isinstance() when testing against a tuple of multiple types? When I do isinstance(x, (Foo, Bar)) a Foo object will be recognized, but a Bar object will not. The same code used to work fine in older versions, including 0.14. Thanks for the report. I did fix one isinstance bug, perhaps I introduced another one (though I thought I tested this...). I'll make sure this works before release. My bad. There was code in Optimize.py, line 2003: if type_check_function not in tests: tests.append(type_check_function) test_nodes.append(...) Basically, it executes each type check function only once, but regardless of the type it is testing against. Works well for builtin types, doesn't work for extension types. https://github.com/cython/cython/commit/c14533e4a00e789df8d800fa9f4cc099faabb67e Hmm, I'm not sure how to merge commits over git branches with hg-git... I've cherry-picked it in. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On Sun, Jan 23, 2011 at 3:16 PM, Arfrever Frehtes Taifersar Arahesis
arfrever@gmail.com wrote:
Test failures with Python 2.7:
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
--
Traceback (most recent call last):
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/Debugger/Tests/TestLibCython.py,
line 177, in setUp
python_version_number = [int(a.strip()) for a in
python_version.strip('()').split(',')[:3]]
ValueError: invalid literal for int() with base 10: 'sys.version_info(major=2'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end basic_cythonize.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/basic_cythonize.srctree'
I think all of these failed because of a unfixed chdir in the failed
debugging test. Please try again with the latest rc.
- Robert
___
Cython-dev mailing list
Cython-dev@codespeak.net
http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On Tue, Jan 18, 2011 at 12:56 AM, Robert Bradshaw rober...@math.washington.edu wrote: A release candidate is up at http://cython.org/release/Cython-0.14.1rc1.tar.gz . Hopefully there shouldn't be many issues, there's just a pile of bugfixes on top of 0.14. I also started http://wiki.cython.org/ReleaseNotes-0.14.1 New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
2011-01-28 11:40:07 Robert Bradshaw napisał(a): New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz Now only Numpy-related tests fail (ticket #630), which is not a regression. -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On Fri, Jan 28, 2011 at 11:40 AM, Robert Bradshaw rober...@math.washington.edu wrote: New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz Is it just me, or do the release candidates break isinstance() when testing against a tuple of multiple types? When I do isinstance(x, (Foo, Bar)) a Foo object will be recognized, but a Bar object will not. The same code used to work fine in older versions, including 0.14. Dominic ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
Dominic Sacré, 29.01.2011 00:38: On Fri, Jan 28, 2011 at 11:40 AM, Robert Bradshaw wrote: New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz Is it just me, or do the release candidates break isinstance() when testing against a tuple of multiple types? When I do isinstance(x, (Foo, Bar)) a Foo object will be recognized, but a Bar object will not. The same code used to work fine in older versions, including 0.14. Yes, looks like a bug: -- cdef class B: pass cdef class C: pass def test_custom_tuple(obj): test_custom_tuple(A()) True test_custom_tuple(B()) True test_custom_tuple(C()) False return isinstance(obj, (A,B)) -- Fails for B(), the second type check is simply dropped. I'm looking into it. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
Robert Bradshaw, 29.01.2011 01:55: On Fri, Jan 28, 2011 at 3:38 PM, Dominic Sacré wrote: On Fri, Jan 28, 2011 at 11:40 AM, Robert Bradshaw wrote: New candidate up at http://cython.org/release/Cython-0.14.1rc3.tar.gz Is it just me, or do the release candidates break isinstance() when testing against a tuple of multiple types? When I do isinstance(x, (Foo, Bar)) a Foo object will be recognized, but a Bar object will not. The same code used to work fine in older versions, including 0.14. Thanks for the report. I did fix one isinstance bug, perhaps I introduced another one (though I thought I tested this...). I'll make sure this works before release. My bad. There was code in Optimize.py, line 2003: if type_check_function not in tests: tests.append(type_check_function) test_nodes.append(...) Basically, it executes each type check function only once, but regardless of the type it is testing against. Works well for builtin types, doesn't work for extension types. https://github.com/cython/cython/commit/c14533e4a00e789df8d800fa9f4cc099faabb67e Hmm, I'm not sure how to merge commits over git branches with hg-git... Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On 24 January 2011 00:16, Arfrever Frehtes Taifersar Arahesis
arfrever@gmail.com wrote:
Test failures with Python 2.7:
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
--
Traceback (most recent call last):
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/Debugger/Tests/TestLibCython.py,
line 177, in setUp
python_version_number = [int(a.strip()) for a in
python_version.strip('()').split(',')[:3]]
ValueError: invalid literal for int() with base 10:
'sys.version_info(major=2'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end basic_cythonize.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/basic_cythonize.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end basic_distutils.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/basic_distutils.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end cpp_cythonize.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/cpp_cythonize.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end cythonize_options.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/cythonize_options.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end inline_distutils.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/inline_distutils.srctree'
==
ERROR: test_embed (__main__.EmbedTest)
--
Traceback (most recent call last):
File runtests.py, line 847, in setUp
os.chdir(self.working_dir)
OSError: [Errno 2] No such file or directory: 'Demos/embed'
==
sys.version_info.__str__() has changed in Python 2.7:
$ python2.6 -c 'import sys; print(sys.version_info)'
(2, 6, 6, 'final', 0)
$ python2.7 -c 'import sys; print(sys.version_info)'
sys.version_info(major=2, minor=7, micro=2, releaselevel='alpha', serial=0)
The first test from the above list fails earlier with Python 3.1:
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
--
Traceback (most recent call last):
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/BUILD/Cy3/Cython/Debugger/Tests/TestLibCython.py,
line 171, in setUp
python_version_script.write('python import sys; print
sys.version_info\n')
TypeError: must be bytes or buffer, not str
Re: [Cython] Cython 0.14.1 release candidate
On Tue, Jan 18, 2011 at 12:56 AM, Robert Bradshaw rober...@math.washington.edu wrote: A release candidate is up at http://cython.org/release/Cython-0.14.1rc1.tar.gz . Hopefully there shouldn't be many issues, there's just a pile of bugfixes on top of 0.14. I also started http://wiki.cython.org/ReleaseNotes-0.14.1 Another candidate up at http://cython.org/release/Cython-0.14.1rc2.tar.gz - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
Test failures with Python 2.7:
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
--
Traceback (most recent call last):
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/Debugger/Tests/TestLibCython.py,
line 177, in setUp
python_version_number = [int(a.strip()) for a in
python_version.strip('()').split(',')[:3]]
ValueError: invalid literal for int() with base 10: 'sys.version_info(major=2'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end basic_cythonize.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/basic_cythonize.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end basic_distutils.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/basic_distutils.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end cpp_cythonize.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/cpp_cythonize.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end cythonize_options.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/cythonize_options.srctree'
==
ERROR: runTest (__main__.EndToEndTest)
End-to-end inline_distutils.srctree
--
Traceback (most recent call last):
File runtests.py, line 797, in setUp
os.path.join('tests', 'build', self.treefile), self.workdir)
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/Cython/TestUtils.py,
line 176, in unpack_source_tree
f = open(tree_file)
IOError: [Errno 2] No such file or directory:
'tests/build/inline_distutils.srctree'
==
ERROR: test_embed (__main__.EmbedTest)
--
Traceback (most recent call last):
File runtests.py, line 847, in setUp
os.chdir(self.working_dir)
OSError: [Errno 2] No such file or directory: 'Demos/embed'
==
sys.version_info.__str__() has changed in Python 2.7:
$ python2.6 -c 'import sys; print(sys.version_info)'
(2, 6, 6, 'final', 0)
$ python2.7 -c 'import sys; print(sys.version_info)'
sys.version_info(major=2, minor=7, micro=2, releaselevel='alpha', serial=0)
The first test from the above list fails earlier with Python 3.1:
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
--
Traceback (most recent call last):
File
/var/tmp/portage/dev-python/cython-0.14.1_rc2/work/Cython-0.14.1rc2/BUILD/Cy3/Cython/Debugger/Tests/TestLibCython.py,
line 171, in setUp
python_version_script.write('python import sys; print sys.version_info\n')
TypeError: must be bytes or buffer, not str
==
I'm attaching untested patch for the first failing test. I didn't have time
to investigate other test failures.
Re: [Cython] Cython 0.14.1 release candidate
Arfrever Frehtes Taifersar Arahesis, 18.01.2011 18:50: IOError: [Errno 2] No such file or directory: '/var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/codefile' I had added the file to setup.py's package_data when I noticed that it was missing, but forgot to add it to MANIFEST.in as well. Mark has fixed that now. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
Test failure with Python 2.6 and 2.7: == FAIL: test_all (Cython.Debugger.Tests.TestLibCython.TestAll) -- Traceback (most recent call last): File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/TestLibCython.py, line 204, in test_all self.assertEquals(0, self.p.wait(), errmsg) AssertionError: ** v INSIDE GDB v ** Python was not compiled with debug symbols (or it was stripped). Some functionality may not work (properly). /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/test_libcython_in_gdb.py:428: UserWarning: Unable to run tests, Python was not compiled with debugging information. Either compile python with -g or get a debug build (configure with --with-pydebug). warnings.warn(msg) ** ^ INSIDE GDB ^ ** == Test suite fails completely with Python 3.1 and 3.2: Python 3.1.3+ (release31-maint:88040, Jan 16 2011, 21:40:20) [GCC 4.4.5] Running tests against Cython 0.14.1rc1 Traceback (most recent call last): File runtests.py, line 1239, in module main() File runtests.py, line 1169, in main collect_unittests(UNITTEST_ROOT, UNITTEST_MODULE + ., test_suite, selectors) File runtests.py, line 713, in collect_unittests module = __import__(modulename) File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/TestLibCython.py, line 25, in module with open(codefile) as f: IOError: [Errno 2] No such file or directory: '/var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/codefile' -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On 18 January 2011 18:50, Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com wrote: Test failure with Python 2.6 and 2.7: == FAIL: test_all (Cython.Debugger.Tests.TestLibCython.TestAll) -- Traceback (most recent call last): File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/TestLibCython.py, line 204, in test_all self.assertEquals(0, self.p.wait(), errmsg) AssertionError: ** v INSIDE GDB v ** Python was not compiled with debug symbols (or it was stripped). Some functionality may not work (properly). /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/test_libcython_in_gdb.py:428: UserWarning: Unable to run tests, Python was not compiled with debugging information. Either compile python with -g or get a debug build (configure with --with-pydebug). warnings.warn(msg) ** ^ INSIDE GDB ^ ** == Test suite fails completely with Python 3.1 and 3.2: Python 3.1.3+ (release31-maint:88040, Jan 16 2011, 21:40:20) [GCC 4.4.5] Running tests against Cython 0.14.1rc1 Traceback (most recent call last): File runtests.py, line 1239, in module main() File runtests.py, line 1169, in main collect_unittests(UNITTEST_ROOT, UNITTEST_MODULE + ., test_suite, selectors) File runtests.py, line 713, in collect_unittests module = __import__(modulename) File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/TestLibCython.py, line 25, in module with open(codefile) as f: IOError: [Errno 2] No such file or directory: '/var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/codefile' -- Arfrever Frehtes Taifersar Arahesis ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Yes, you need to run those tests with a python build for which debug symbols are available. Should I turn this into a warning instead of an error? ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On 18 January 2011 18:54, mark florisson markflorisso...@gmail.com wrote: On 18 January 2011 18:50, Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com wrote: Test failure with Python 2.6 and 2.7: == FAIL: test_all (Cython.Debugger.Tests.TestLibCython.TestAll) -- Traceback (most recent call last): File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/TestLibCython.py, line 204, in test_all self.assertEquals(0, self.p.wait(), errmsg) AssertionError: ** v INSIDE GDB v ** Python was not compiled with debug symbols (or it was stripped). Some functionality may not work (properly). /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/Cython/Debugger/Tests/test_libcython_in_gdb.py:428: UserWarning: Unable to run tests, Python was not compiled with debugging information. Either compile python with -g or get a debug build (configure with --with-pydebug). warnings.warn(msg) ** ^ INSIDE GDB ^ ** == Test suite fails completely with Python 3.1 and 3.2: Python 3.1.3+ (release31-maint:88040, Jan 16 2011, 21:40:20) [GCC 4.4.5] Running tests against Cython 0.14.1rc1 Traceback (most recent call last): File runtests.py, line 1239, in module main() File runtests.py, line 1169, in main collect_unittests(UNITTEST_ROOT, UNITTEST_MODULE + ., test_suite, selectors) File runtests.py, line 713, in collect_unittests module = __import__(modulename) File /var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/TestLibCython.py, line 25, in module with open(codefile) as f: IOError: [Errno 2] No such file or directory: '/var/tmp/portage/dev-python/cython-0.14.1_rc1/work/Cython-0.14.1rc1/BUILD/Cy3/Cython/Debugger/Tests/codefile' For this I think I will need to change it to a python module (codefile.py) to have setup.py include it in the installation. I will push a fix shortly. -- Arfrever Frehtes Taifersar Arahesis ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Yes, you need to run those tests with a python build for which debug symbols are available. Should I turn this into a warning instead of an error? ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On an unrelated side note, should we modify the testrunner to continue when importing a test module fails and have it print a traceback instead? ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
2011-01-18 18:54:03 mark florisson napisał(a): Yes, you need to run those tests with a python build for which debug symbols are available. Should I turn this into a warning instead of an error? This test should be automatically skipped when debug symbols are unavailable. -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On Tue, Jan 18, 2011 at 10:07 AM, mark florisson markflorisso...@gmail.com wrote: On an unrelated side note, should we modify the testrunner to continue when importing a test module fails and have it print a traceback instead? Yes, that would make the most sense. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1 release candidate
On Tue, Jan 18, 2011 at 10:09 AM, Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com wrote: 2011-01-18 18:54:03 mark florisson napisał(a): Yes, you need to run those tests with a python build for which debug symbols are available. Should I turn this into a warning instead of an error? This test should be automatically skipped when debug symbols are unavailable. +1 Mark, you should be able to push now. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel stefan...@behnel.de wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. And, no, that's not a green card for back doors. ;-) :) - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw rober...@math.washington.edu wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel stefan...@behnel.de wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. Note that this brings up http://trac.cython.org/cython_trac/ticket/645 . I'd say we're ready for an rc. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Is that a missing commit? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 14 January 2011 12:06, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? Is that a missing commit? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 14 January 2011 12:08, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:06, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? Is that a missing commit? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Fri, Jan 14, 2011 at 3:08 AM, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:06, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? It was added to line 103 from setup.py, but not to the repo? - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 14 January 2011 12:11, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:08, mark florisson markflorisso...@gmail.comwrote: On 14 January 2011 12:06, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? Is that a missing commit? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. With that change it should build and install correctly. If you want I can also push, but you'd have to pull. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
mark florisson, 14.01.2011 12:08: On 14 January 2011 12:06, Stefan Behnelstefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? https://sage.math.washington.edu:8091/hudson/job/cython-devel-build-py2-trunk/744/console setup.py says: compiled_modules = [Cython.Plex.Scanners, Cython.Plex.Actions, ..., Cython.Runtime.refnanny, Cython.Debugger.do_repeat,] So, you're suggesting that this line can be removed? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Fri, Jan 14, 2011 at 3:11 AM, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:08, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:06, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 10:05: On Fri, Jan 14, 2011 at 12:02 AM, Robert Bradshaw wrote: On Thu, Jan 13, 2011 at 11:53 PM, Stefan Behnel wrote: mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. I'm actually looking at that code right now. I've merged this. The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx I don't have it, how does it complain? Is that a missing commit? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
Robert Bradshaw, 14.01.2011 12:12: On Fri, Jan 14, 2011 at 3:11 AM, mark florisson wrote: On 14 January 2011 12:08, mark florisson wrote: On 14 January 2011 12:06, Stefan Behnel wrote: The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. Ok, that looks better. Now that the debugger support is an official feature, should we have a Hudson job that builds Cython and all tests with gdb support enabled? Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Fri, Jan 14, 2011 at 3:27 AM, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 12:12: On Fri, Jan 14, 2011 at 3:11 AM, mark florisson wrote: On 14 January 2011 12:08, mark florisson wrote: On 14 January 2011 12:06, Stefan Behnel wrote: The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. Ok, that looks better. Now that the debugger support is an official feature, should we have a Hudson job that builds Cython and all tests with gdb support enabled? Yes, that would make sense. We'd have to build our own newer gdb of course, and a debug version of Python. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 14 January 2011 12:31, Robert Bradshaw rober...@math.washington.eduwrote: On Fri, Jan 14, 2011 at 3:27 AM, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 12:12: On Fri, Jan 14, 2011 at 3:11 AM, mark florisson wrote: On 14 January 2011 12:08, mark florisson wrote: On 14 January 2011 12:06, Stefan Behnel wrote: The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. Ok, that looks better. Now that the debugger support is an official feature, should we have a Hudson job that builds Cython and all tests with gdb support enabled? Yes, that would make sense. We'd have to build our own newer gdb of course, and a debug version of Python. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev That would be great. In that case, is it possible that my branch will make it to Hudson? Otherwise Hudson will only be useful after merging into mainline, which is probably just a few hours or days before the release. In any case it would also help prevent for instance the issue we had now where my branch did introduce a problem just before the release (in the future I will run the full test suite instead of skipping some of them with those options to runtests.py). If that's a hassle I wouldn't mind mainline branch access either, I promise I'll be good :) The important thing is Python with debug symbols, it does not necessarily have to be a debug build. The thing is that at least many Linux distros ship debug symbols with the debug build (usually Python is compiled with -g, but then stripped). This is for instance the case in Ubuntu (and probably Debian). However, in Fedora for instance even the debug build is shipped without symbols, and they need to be installed separately. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
mark florisson, 14.01.2011 12:45: is it possible that my branch will make it to Hudson? [...] If that's a hassle I wouldn't mind mainline branch access either, I promise I'll be good :) I'm ok with giving you write access to the main branch, so that you can merge your changes over yourself. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On Fri, Jan 14, 2011 at 3:45 AM, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:31, Robert Bradshaw rober...@math.washington.edu wrote: On Fri, Jan 14, 2011 at 3:27 AM, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 12:12: On Fri, Jan 14, 2011 at 3:11 AM, mark florisson wrote: On 14 January 2011 12:08, mark florisson wrote: On 14 January 2011 12:06, Stefan Behnel wrote: The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. Ok, that looks better. Now that the debugger support is an official feature, should we have a Hudson job that builds Cython and all tests with gdb support enabled? Yes, that would make sense. We'd have to build our own newer gdb of course, and a debug version of Python. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev That would be great. In that case, is it possible that my branch will make it to Hudson? Otherwise Hudson will only be useful after merging into mainline, which is probably just a few hours or days before the release. In any case it would also help prevent for instance the issue we had now where my branch did introduce a problem just before the release (in the future I will run the full test suite instead of skipping some of them with those options to runtests.py). If that's a hassle I wouldn't mind mainline branch access either, I promise I'll be good :) I've read enough of your code that I think that'd be fine. I think it makes sense to have a separate branch for the debugger stuff so things could be caught before merging. The important thing is Python with debug symbols, it does not necessarily have to be a debug build. The thing is that at least many Linux distros ship debug symbols with the debug build (usually Python is compiled with -g, but then stripped). This is for instance the case in Ubuntu (and probably Debian). However, in Fedora for instance even the debug build is shipped without symbols, and they need to be installed separately. We build our own Pythons, so could include debug symbols in them. Other than that, is the only requirement to have a working gdb = 7.2 in the path somewhere? - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 14 January 2011 19:06, Robert Bradshaw rober...@math.washington.eduwrote: On Fri, Jan 14, 2011 at 3:45 AM, mark florisson markflorisso...@gmail.com wrote: On 14 January 2011 12:31, Robert Bradshaw rober...@math.washington.edu wrote: On Fri, Jan 14, 2011 at 3:27 AM, Stefan Behnel stefan...@behnel.de wrote: Robert Bradshaw, 14.01.2011 12:12: On Fri, Jan 14, 2011 at 3:11 AM, mark florisson wrote: On 14 January 2011 12:08, mark florisson wrote: On 14 January 2011 12:06, Stefan Behnel wrote: The build complains because it cannot find a file called Cython/Debugger/do_repeat.pyx Apparently something left that should have been removed, apologies. You can remove it from the setup.py in the list on line 104. Done. Ok, that looks better. Now that the debugger support is an official feature, should we have a Hudson job that builds Cython and all tests with gdb support enabled? Yes, that would make sense. We'd have to build our own newer gdb of course, and a debug version of Python. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev That would be great. In that case, is it possible that my branch will make it to Hudson? Otherwise Hudson will only be useful after merging into mainline, which is probably just a few hours or days before the release. In any case it would also help prevent for instance the issue we had now where my branch did introduce a problem just before the release (in the future I will run the full test suite instead of skipping some of them with those options to runtests.py). If that's a hassle I wouldn't mind mainline branch access either, I promise I'll be good :) I've read enough of your code that I think that'd be fine. I think it makes sense to have a separate branch for the debugger stuff so things could be caught before merging. The important thing is Python with debug symbols, it does not necessarily have to be a debug build. The thing is that at least many Linux distros ship debug symbols with the debug build (usually Python is compiled with -g, but then stripped). This is for instance the case in Ubuntu (and probably Debian). However, in Fedora for instance even the debug build is shipped without symbols, and they need to be installed separately. We build our own Pythons, so could include debug symbols in them. Other than that, is the only requirement to have a working gdb = 7.2 in the path somewhere? Yes. And gdb must be build with Python support, but I believe that that's the default. - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 13 January 2011 11:39, Stefan Behnel stefan...@behnel.de wrote: Hi, I looked through the tickets that are scheduled for 0.14.1 but couldn't see any that are truly critical, especially no regressions. http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 I think we fixed all known bugs that appeared with 0.14 by now, so I'd say it's time for at least a release candidate. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Great, I presume the pending pull requests will be merged for this release? ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
mark florisson, 13.01.2011 11:42: On 13 January 2011 11:39, Stefan Behnel wrote: I looked through the tickets that are scheduled for 0.14.1 but couldn't see any that are truly critical, especially no regressions. http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 I think we fixed all known bugs that appeared with 0.14 by now, so I'd say it's time for at least a release candidate. Great, I presume the pending pull requests will be merged for this release? The test runner change by Vitja should be ok. Can't comment on the debugging changes. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 01/13/2011 11:42 AM, mark florisson wrote: On 13 January 2011 11:39, Stefan Behnel stefan...@behnel.de mailto:stefan...@behnel.de wrote: Hi, I looked through the tickets that are scheduled for 0.14.1 but couldn't see any that are truly critical, especially no regressions. http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 I think we fixed all known bugs that appeared with 0.14 by now, so I'd say it's time for at least a release candidate. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net mailto:Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Great, I presume the pending pull requests will be merged for this release? As we use Trac to coordinate fixes with releases I think it'd be good if we went into the habit of always creating a small Trac ticket for each pull request. (If we move to the github tracker, I suppose this will happen automatically, but for now we should do it manually.) Your pull request is now http://trac.cython.org/cython_trac/ticket/642 Dag Sverre ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
Dag Sverre Seljebotn, 13.01.2011 11:56: As we use Trac to coordinate fixes with releases I think it'd be good if we went into the habit of always creating a small Trac ticket for each pull request. +1. My immediate thoughts were oh great, one place more to look before a release Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 13 January 2011 11:56, Dag Sverre Seljebotn da...@student.matnat.uio.nowrote: On 01/13/2011 11:42 AM, mark florisson wrote: On 13 January 2011 11:39, Stefan Behnel stefan...@behnel.de wrote: Hi, I looked through the tickets that are scheduled for 0.14.1 but couldn't see any that are truly critical, especially no regressions. http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 I think we fixed all known bugs that appeared with 0.14 by now, so I'd say it's time for at least a release candidate. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Great, I presume the pending pull requests will be merged for this release? As we use Trac to coordinate fixes with releases I think it'd be good if we went into the habit of always creating a small Trac ticket for each pull request. (If we move to the github tracker, I suppose this will happen automatically, but for now we should do it manually.) Your pull request is now http://trac.cython.org/cython_trac/ticket/642 Dag Sverre ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev Ok, sounds fine. In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome however, as it supports fast Python stepping and stepping over (by using a watchpoint on the bytecode instruction pointer instead of a step-over loop), support for closures, the debugger now also detects when there is a pending exception in Python code, there are more tests, and additionally I fixed the debug command line flags such as --debug-trace-code-generation, as the module which set the code tracer functionality globally through a metaclass was imported before the command line option was processed. So basically I think the code could be reviewed by running the testsuite and by looking at which files outside the Cython.Debugger package were changed in what way. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
On 13 January 2011 07:39, Stefan Behnel stefan...@behnel.de wrote: Hi, I looked through the tickets that are scheduled for 0.14.1 but couldn't see any that are truly critical, especially no regressions. It would be nice to make a testsuite run in Windows (32 and 64, with MSVC and MinGW) before the release. However, I'm not able to do that until Monday... http://trac.cython.org/cython_trac/query?status=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=0.14.1 I think we fixed all known bugs that appeared with 0.14 by now, so I'd say it's time for at least a release candidate. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev -- Lisandro Dalcin --- CIMEC (INTEC/CONICET-UNL) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo Tel: +54-342-4511594 (ext 1011) Tel/Fax: +54-342-4511169 ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1?
mark florisson, 13.01.2011 12:05: In any case, there are virtually no changes when the --gdb flag is inactive. These last additions would be very welcome [...] Ok, here's a general statement. I personally consider the debugging support new, experimental and not a critical feature for compiler or language. You are the current maintainer of that part anyway, so I'm fine with merging the changes for 0.14.1, even unseen, as long as it doesn't break anything that's more important. And, no, that's not a green card for back doors. ;-) Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1
Arfrever Frehtes Taifersar Arahesis, 26.12.2010 12:58: 2010-12-26 09:46:48 Stefan Behnel napisał(a): regarding the next release, I think we should fix the ref-counting bug that Martijn Meijers found (ticket #633) and then release 0.14.1 ASAP from the current git tip, which already has a couple of other bug fixes. It would be nice if compatibility with Numpy 1.5 was fixed (ticket #630). IMHO, that's not the same level of criticality as a serious crash bug, so unless someone provides a ready-to-review-and-merge patch for #630, I'd prefer getting 0.14.1 out without waiting for a fix. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1
On Mon, Dec 27, 2010 at 12:07 AM, Stefan Behnel stefan...@behnel.de wrote: Arfrever Frehtes Taifersar Arahesis, 26.12.2010 12:58: 2010-12-26 09:46:48 Stefan Behnel napisał(a): regarding the next release, I think we should fix the ref-counting bug that Martijn Meijers found (ticket #633) and then release 0.14.1 ASAP from the current git tip, which already has a couple of other bug fixes. My thoughts exactly. It would be nice if compatibility with Numpy 1.5 was fixed (ticket #630). IMHO, that's not the same level of criticality as a serious crash bug, so unless someone provides a ready-to-review-and-merge patch for #630, I'd prefer getting 0.14.1 out without waiting for a fix. I agree. There's a fair number of fixes in the tree already, so I was actually thinking about doing a 0.14.1 release soon anyways. Of course something big like this necessitates a quicker release, but how about we see what fixes we can get in this next release and release first thing in January? - Robert ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1
Robert Bradshaw, 27.12.2010 17:36: On Mon, Dec 27, 2010 at 12:07 AM, Stefan Behnel wrote: Arfrever Frehtes Taifersar Arahesis, 26.12.2010 12:58: 2010-12-26 09:46:48 Stefan Behnel napisał(a): regarding the next release, I think we should fix the ref-counting bug that Martijn Meijers found (ticket #633) and then release 0.14.1 ASAP from the current git tip, which already has a couple of other bug fixes. My thoughts exactly. It would be nice if compatibility with Numpy 1.5 was fixed (ticket #630). IMHO, that's not the same level of criticality as a serious crash bug, so unless someone provides a ready-to-review-and-merge patch for #630, I'd prefer getting 0.14.1 out without waiting for a fix. I agree. There's a fair number of fixes in the tree already, so I was actually thinking about doing a 0.14.1 release soon anyways. Of course something big like this necessitates a quicker release, but how about we see what fixes we can get in this next release and release first thing in January? +1, that should be close enough. Stefan ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
Re: [Cython] Cython 0.14.1
2010-12-26 09:46:48 Stefan Behnel napisał(a): regarding the next release, I think we should fix the ref-counting bug that Martijn Meijers found (ticket #633) and then release 0.14.1 ASAP from the current git tip, which already has a couple of other bug fixes. It would be nice if compatibility with Numpy 1.5 was fixed (ticket #630). -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part. ___ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
