Re: [Cython] Bugfix release
just to make sure -- 0.15.1 would come out from 'release' branch, right? (there is motion to get fresh cython into debian and I am arguing that it would be better to take post 0.15 snapshot) On Tue, 13 Sep 2011, Robert Bradshaw wrote: > > I guess we're set for a release then, right? > +1. Should we send a release candidate around, or just cut it (as it > is bugfix-only and hasn't been too long since the last one)? > Also, is there a parameterized jenkins target for the release branch > yet (I'm not seeing it)? -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Bugfix release
Yaroslav Halchenko, 15.09.2011 17:08: On Tue, 13 Sep 2011, Robert Bradshaw wrote: I guess we're set for a release then, right? +1. Should we send a release candidate around, or just cut it (as it is bugfix-only and hasn't been too long since the last one)? Also, is there a parameterized jenkins target for the release branch yet (I'm not seeing it)? just to make sure -- 0.15.1 would come out from 'release' branch, right? Yes. (there is motion to get fresh cython into debian and I am arguing that it would be better to take post 0.15 snapshot) I would hope that we get the release out rather soon, so there's no need to use a snapshot. Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Bugfix release
On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote: > Yaroslav Halchenko, 15.09.2011 17:08: >> >> On Tue, 13 Sep 2011, Robert Bradshaw wrote: I guess we're set for a release then, right? >> >>> +1. Should we send a release candidate around, or just cut it (as it >>> is bugfix-only and hasn't been too long since the last one)? >> >>> Also, is there a parameterized jenkins target for the release branch >>> yet (I'm not seeing it)? >> >> just to make sure -- 0.15.1 would come out from 'release' branch, >> right? > > Yes. > > >> (there is motion to get fresh cython into debian and I am arguing >> that it would be better to take post 0.15 snapshot) > > I would hope that we get the release out rather soon, so there's no need to > use a snapshot. Anything in particular we're waiting on? I put up http://wiki.cython.org/ReleaseNotes-0.15.1 - Robert ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
[Cython] Cython 0.15.1 release candidate
See http://wiki.cython.org/ReleaseNotes-0.15.1 This is a bugfix only release, we hope to get it out shortly. - Robert ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Bugfix release
Robert Bradshaw, 15.09.2011 22:31: On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote: Yaroslav Halchenko, 15.09.2011 17:08: On Tue, 13 Sep 2011, Robert Bradshaw wrote: I guess we're set for a release then, right? +1. Should we send a release candidate around, or just cut it (as it is bugfix-only and hasn't been too long since the last one)? Also, is there a parameterized jenkins target for the release branch yet (I'm not seeing it)? just to make sure -- 0.15.1 would come out from 'release' branch, right? Yes. (there is motion to get fresh cython into debian and I am arguing that it would be better to take post 0.15 snapshot) I would hope that we get the release out rather soon, so there's no need to use a snapshot. Anything in particular we're waiting on? For you to do it. ;) I put up http://wiki.cython.org/ReleaseNotes-0.15.1 Yes, that's about it. Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Bugfix release
On Thu, Sep 15, 2011 at 1:38 PM, Stefan Behnel wrote: > Robert Bradshaw, 15.09.2011 22:31: >> >> On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote: >>> >>> Yaroslav Halchenko, 15.09.2011 17:08: On Tue, 13 Sep 2011, Robert Bradshaw wrote: >> >> I guess we're set for a release then, right? > +1. Should we send a release candidate around, or just cut it (as it > is bugfix-only and hasn't been too long since the last one)? > Also, is there a parameterized jenkins target for the release branch > yet (I'm not seeing it)? just to make sure -- 0.15.1 would come out from 'release' branch, right? >>> >>> Yes. >>> >>> (there is motion to get fresh cython into debian and I am arguing that it would be better to take post 0.15 snapshot) >>> >>> I would hope that we get the release out rather soon, so there's no need >>> to >>> use a snapshot. >> >> Anything in particular we're waiting on? > > For you to do it. ;) :) I sent an RC out, so we'll see if we get any feedback, but I don't see any reason to have a long wait before pushing this out. - Robert ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython 0.15.1 release candidate
1 test failure with Python 2.6: compiling (c) and running tupleunpack_T712 ... Doctest: tupleunpack_T712.__test__.single_from_set (line 12) ... ok Doctest: tupleunpack_T712.__test__.single_from_string (line 4) ... ok compiling (cpp) and running tupleunpack_T712 ... cc1plus: warning: command line option "-Wpointer-sign" is valid for C/ObjC but not for C++ tupleunpack_T712.cpp: In function ‘PyObject* __pyx_pf_16tupleunpack_T712_1single_from_set(PyObject*, PyObject*)’: tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ tupleunpack_T712.cpp:642:151: error: from here tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t index’ tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ tupleunpack_T712.cpp:640:135: error: from here tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t index’ ERROR -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part. ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython 0.15.1 release candidate
1 error ("compiling (cpp) and running tupleunpack_T712") and 0 failures with
Python 3.1.
1 error ("compiling (cpp) and running tupleunpack_T712") and 4 failures with
Python 3.2.
The end of output of tests with Python 3.2:
==
ERROR: runTest (__main__.CythonRunTestCase)
compiling (cpp) and running tupleunpack_T712
--
Traceback (most recent call last):
File "/usr/lib64/python3.2/distutils/unixccompiler.py", line 181, in _compile
extra_postargs)
File "/usr/lib64/python3.2/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/usr/lib64/python3.2/distutils/spawn.py", line 32, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/usr/lib64/python3.2/distutils/spawn.py", line 163, in _spawn_posix
% (cmd[0], exit_status))
distutils.errors.DistutilsExecError: command 'x86_64-pc-linux-gnu-g++' failed
with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "runtests.py", line 678, in run
self.runCompileTest()
File "runtests.py", line 490, in runCompileTest
self.test_directory, self.expect_errors, self.annotate)
File "runtests.py", line 665, in compile
self.run_distutils(test_directory, module, workdir, incdir)
File "runtests.py", line 625, in run_distutils
build_extension.run()
File "/usr/lib64/python3.2/distutils/command/build_ext.py", line 345, in run
self.build_extensions()
File "/usr/lib64/python3.2/distutils/command/build_ext.py", line 454, in
build_extensions
self.build_extension(ext)
File "runtests.py", line 257, in build_extension
_build_ext.build_extension(self, ext)
File "/usr/lib64/python3.2/distutils/command/build_ext.py", line 509, in
build_extension
depends=ext.depends)
File "/usr/lib64/python3.2/distutils/ccompiler.py", line 574, in compile
self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
File "/usr/lib64/python3.2/distutils/unixccompiler.py", line 186, in _compile
raise CompileError(msg)
distutils.errors.CompileError: command 'x86_64-pc-linux-gnu-g++' failed with
exit status 1
==
FAIL: NestedWith (withstat)
Doctest: withstat.NestedWith
--
Traceback (most recent call last):
File "/usr/lib64/python3.2/doctest.py", line 2118, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for withstat.NestedWith
File
"/var/tmp/portage/dev-python/cython-0.15.1_rc0/work/Cython-0.15.1/tests-3.2/run/c/withstat.cpython-32.so",
line unknown line number, in NestedWith
--
File
"/var/tmp/portage/dev-python/cython-0.15.1_rc0/work/Cython-0.15.1/tests-3.2/run/c/withstat.cpython-32.so",
line ?, in withstat.NestedWith
Failed example:
NestedWith().runTest()
Exception raised:
Traceback (most recent call last):
File "/usr/lib64/python3.2/doctest.py", line 1253, in __run
compileflags, 1), test.globs)
File "", line 1, in
NestedWith().runTest()
File "withstat.pyx", line 183, in withstat.NestedWith.runTest
(withstat.c:5076)
File "withstat.pyx", line 222, in
withstat.NestedWith.testEnterReturnsTuple (withstat.c:7533)
File "withstat.pyx", line 223, in
withstat.NestedWith.testEnterReturnsTuple (withstat.c:7421)
File "withstat.pyx", line 224, in
withstat.NestedWith.testEnterReturnsTuple (withstat.c:7270)
File "/usr/lib64/python3.2/unittest/case.py", line 1169, in
deprecated_func
DeprecationWarning, 2)
File "/usr/lib64/python3.2/warnings.py", line 18, in showwarning
file.write(formatwarning(message, category, filename, lineno, line))
File "/usr/lib64/python3.2/warnings.py", line 25, in formatwarning
line = linecache.getline(filename, lineno) if line is None else line
File "/usr/lib64/python3.2/linecache.py", line 15, in getline
lines = getlines(filename, module_globals)
File "/usr/lib64/python3.2/doctest.py", line 1337, in
__patched_linecache_getlines
return self.save_linecache_getlines(filename, module_globals)
File "/usr/lib64/python3.2/linecache.py", line 41, in getlines
return updatecache(filename, module_globals)
File "/usr/lib64/python3.2/linecache.py", line 127, in updatecache
lines = fp.readlines()
File "/usr/lib64/python3.2/codecs.py", line 300, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xd0 in position 24:
invalid continuation byte
==
FAIL: NestedWith (withstat)
Doctest: withsta
Re: [Cython] Cython 0.15.1 release candidate
2011/9/16 Arfrever Frehtes Taifersar Arahesis : > 1 test failure with Python 2.6: > > compiling (c) and running tupleunpack_T712 ... Doctest: > tupleunpack_T712.__test__.single_from_set (line 12) ... ok > Doctest: tupleunpack_T712.__test__.single_from_string (line 4) ... ok > compiling (cpp) and running tupleunpack_T712 ... cc1plus: warning: command > line option "-Wpointer-sign" is valid for C/ObjC but not for C++ > tupleunpack_T712.cpp: In function ‘PyObject* > __pyx_pf_16tupleunpack_T712_1single_from_set(PyObject*, PyObject*)’: > tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ > tupleunpack_T712.cpp:642:151: error: from here > tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t > index’ > tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ > tupleunpack_T712.cpp:640:135: error: from here > tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t > index’ > ERROR > Robert, It seems that you created tarball from old revision. -- vitja. ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython 0.15.1 release candidate
On Thu, Sep 15, 2011 at 9:10 PM, Vitja Makarov wrote: > 2011/9/16 Arfrever Frehtes Taifersar Arahesis : >> 1 test failure with Python 2.6: >> >> compiling (c) and running tupleunpack_T712 ... Doctest: >> tupleunpack_T712.__test__.single_from_set (line 12) ... ok >> Doctest: tupleunpack_T712.__test__.single_from_string (line 4) ... ok >> compiling (cpp) and running tupleunpack_T712 ... cc1plus: warning: command >> line option "-Wpointer-sign" is valid for C/ObjC but not for C++ >> tupleunpack_T712.cpp: In function ‘PyObject* >> __pyx_pf_16tupleunpack_T712_1single_from_set(PyObject*, PyObject*)’: >> tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ >> tupleunpack_T712.cpp:642:151: error: from here >> tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t >> index’ >> tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ >> tupleunpack_T712.cpp:640:135: error: from here >> tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t >> index’ >> ERROR >> > > Robert, It seems that you created tarball from old revision. I just downloaded http://cython.org/release/Cython-0.15.1rc0.tar.gz and unpacked it, the latest commit is commit 34f6211d53485df1ba25cfeb9c414045b095f57d Author: Stefan Behnel Date: Wed Sep 14 21:37:09 2011 +0200 which seems right. - Robert ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython 0.15.1 release candidate
2011/9/16 Robert Bradshaw : > On Thu, Sep 15, 2011 at 9:10 PM, Vitja Makarov > wrote: >> 2011/9/16 Arfrever Frehtes Taifersar Arahesis : >>> 1 test failure with Python 2.6: >>> >>> compiling (c) and running tupleunpack_T712 ... Doctest: >>> tupleunpack_T712.__test__.single_from_set (line 12) ... ok >>> Doctest: tupleunpack_T712.__test__.single_from_string (line 4) ... ok >>> compiling (cpp) and running tupleunpack_T712 ... cc1plus: warning: command >>> line option "-Wpointer-sign" is valid for C/ObjC but not for C++ >>> tupleunpack_T712.cpp: In function ‘PyObject* >>> __pyx_pf_16tupleunpack_T712_1single_from_set(PyObject*, PyObject*)’: >>> tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ >>> tupleunpack_T712.cpp:642:151: error: from here >>> tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t >>> index’ >>> tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ >>> tupleunpack_T712.cpp:640:135: error: from here >>> tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t >>> index’ >>> ERROR >>> >> >> Robert, It seems that you created tarball from old revision. > > I just downloaded http://cython.org/release/Cython-0.15.1rc0.tar.gz > and unpacked it, the latest commit is > > commit 34f6211d53485df1ba25cfeb9c414045b095f57d > Author: Stefan Behnel > Date: Wed Sep 14 21:37:09 2011 +0200 > > which seems right. > Right. Sorry, I did compare it to wrong branch. Btw I'm sure that we have seen this error before: compiling (c) and running tupleunpack_T712 ... Doctest: tupleunpack_T712.__test__.single_from_set (line 12) ... ok Doctest: tupleunpack_T712.__test__.single_from_string (line 4) ... ok compiling (cpp) and running tupleunpack_T712 ... cc1plus: warning: command line option "-Wpointer-sign" is valid for C/ObjC but not for C++ tupleunpack_T712.cpp: In function ‘PyObject* __pyx_pf_16tupleunpack_T712_1single_from_set(PyObject*, PyObject*)’: tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ tupleunpack_T712.cpp:642:151: error: from here tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t index’ tupleunpack_T712.cpp:681:3: error: jump to label ‘__pyx_L1_error’ tupleunpack_T712.cpp:640:135: error: from here tupleunpack_T712.cpp:644:14: error: crosses initialization of ‘Py_ssize_t index’ ERROR -- vitja. ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython 0.15.1 release candidate
Arfrever Frehtes Taifersar Arahesis, 16.09.2011 05:24:
1 error ("compiling (cpp) and running tupleunpack_T712") and 0 failures with
Python 3.1.
1 error ("compiling (cpp) and running tupleunpack_T712") and 4 failures with
Python 3.2.
==
FAIL: NestedWith (withstat)
Doctest: withstat.NestedWith
--
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc0 in position 24:
invalid start byte
==
FAIL: NestedWith (withstat_py)
Doctest: withstat_py.NestedWith
--
UnicodeDecodeError: 'utf8' codec can't decode byte 0x90 in position 40:
invalid start byte
Nice - that means we are compliant with Python itself here! ;)
More seriously, it also means we must test the release branch under Python
3 on Jenkins. That's much easier to do now, I can just copy the three
build/test jobs, so that we get complete test coverage for it. Given how
rare it usually is that we push to the release branch, That won't hurt, but
it will give us much better safety for releases.
Stefan
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
