[Cython] Release branch usage
mark florisson, 23.03.2012 15:29: > On 23 March 2012 14:24, Stefan Behnel wrote: >> mark florisson, 23.03.2012 15:09: >>> I also changed the cython-sdist to pull from the release0.16 >>> branch, to make sure things work in the release. >> >> There are dedicated cython-release jobs for that. Not sure in what >> state they are (haven't been used for a while), but they were supposed >> to work on the "release" branch. If you had named the branch plain >> "release", they would have done the right thing. > > Ok I'll rename the release branch then. Thanks. Basically, I think the way the "release" branch should be used is just to collect the release relevant changes up to the release, and once that's done (and there's a tag for the release), it should simply be merged back into the master branch to die there. That way, we can recreate it for each new release, including emergency fix releases, which would go on top of the release tag. Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] some pull requests for 0.16?
mark florisson, 20.03.2012 17:40: > Finally, there is a serious bug in the reversed(range()) optimization > that Mike Graham discovered when working on the range() optimization > with a runtime step, which is basically wrong for any step that is not > 1 or -1 (it simply swaps the bounds with an offset by 1, but it > actually has to figure out what the actual last value was in the range > and use that as the start instead). I personally consider this a > blocker, so I'll try contacting Mike and see if he is still > (interested in) working on that. I've disabled the optimisation in the release branch. https://github.com/cython/cython/commit/f766a7fc2a4b7fa67b2db8592034980bff9c5783 Given that this didn't work before, disabling it isn't a regression, so I've closed the ticket (#763) and added a new one as request for optimisation (#765). Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] NumPy test failures in Py2.4
On 23 March 2012 19:40, Stefan Behnel wrote:
> Hi,
>
> after re-enabling the NumPy tests, I'm getting two NumPy (1.6.1) test
> failure in Py2.4 (2.7 is ok):
>
> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/BACKEND=c,PYVERSION=py24-ext/224/testReport/junit/doctest/DocTestCase/Doctest__numpy_test/
>
> """
> File ".../run/c/numpy_test.so", line 207, in numpy_test
> Failed example:
> print(test_partially_packed_align(np.zeros((1,), dtype=np.dtype([('a',
> 'b'), ('b', 'i'), ('sub', np.dtype('b,i')), ('c', 'i')], align=True
> Exception raised:
> Traceback (most recent call last):
> File "numpy_test.pyx", line 451, in
> numpy_test.test_partially_packed_align (numpy_test.c:7967)
> ValueError: Buffer dtype mismatch; next field is at offset 13 but 16
> expected
> --
> File ".../run/c/numpy_test.so", line 211, in numpy_test
> Failed example:
> print(test_partially_packed_align_2(np.zeros((1,),
> dtype=np.dtype([('a', 'b'), ('b', 'i'), ('c', 'b'), ('sub', np.dtype('b,i',
> align=True))]
> Exception raised:
> File "numpy_test.pyx", line 459, in
> numpy_test.test_partially_packed_align_2 (numpy_test.c:8186)
> ValueError: Buffer dtype mismatch; next field is at offset 7 but 10
> expected
> """
>
> Does anyone know what to make of this?
That's probably a regression from my changes to the buffer format
parser. It should be aligning on the second integer in the substruct,
for which the entire struct is aligned and the first character padded.
I'll look into it, thanks.
> Stefan
> ___
> cython-devel mailing list
> cython-devel@python.org
> http://mail.python.org/mailman/listinfo/cython-devel
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] NumPy dependency in Jenkins builds
On 23 March 2012 19:48, Stefan Behnel wrote: > Stefan Behnel, 23.03.2012 15:26: >> mark florisson, 23.03.2012 14:26: >>> This may be OT for this thread >> >> ... in which case it's quite common to start a new one ... >> >>> but sas numpy removed at some point from Jenkins? I'm seeing this for >>> all python versions since Februari 25: >>> >>> Following tests excluded because of missing dependencies on your >>> system: >>> run.memoryviewattrs >>> run.numpy_ValueError_T172 >>> run.numpy_bufacc_T155 >>> run.numpy_cimport >>> run.numpy_memoryview >>> run.numpy_parallel >>> run.numpy_test >>> ALL DONE >> >> May be my fault. I think when I unified the build jobs, I might have >> disabled it because we didn't have a NumPy version for Py3 at the time. >> >> I'll look into it. > > I've re-enabled them for all CPython builds except for the latest py3k > branch. NumPy 1.6.1 doesn't compile there due to the new Unicode buffer > layout (PEP 383). > > Stefan > ___ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel Thanks, that's really useful. ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
