is it always this particular test?
> On Wed, Nov 30, 2016 at 6:46 AM, Yaroslav Halchenko
> wrote:
> > A fresh one I ran into while rebuilding with fixes for 32bit (thanks
> > BTW! sorry for not prompt followup/gratitude)
> > ===
On Tue, 24 Jan 2017, Robert Bradshaw wrote:
> Ah, if the enum is unsigned and has the same size as unsigned long, this
> could happen. I pushed
> https://github.com/cython/cython/commit/d92a718a26c9354fbf35f31a17de5c069865a447
> for future release.
Great -- thank you! meanwhile used the same "w
Dear Cython gurus,
How to skip this test?
It is causing failures on i386:
https://github.com/cython/cython/issues/1548
and I have tried to skip it, so my test running line now is
set -e; for P in 2.7 3.5; do \
PYTHONPATH=`/bin/ls -d /build/cython-0.25.2/build/lib.*-$P` \
/usr/bin/python$P run
A fresh one I ran into while rebuilding with fixes for 32bit (thanks
BTW! sorry for not prompt followup/gratitude)
==
ERROR: runTest (__main__.CythonRunTestCase)
compiling (cpp) and running builtin_subtype_methods_T653
---
On Thu, 17 Nov 2016, Robert Bradshaw wrote:
> I'm preparing another bugfix release. Try it out at
> https://github.com/cython/cython/archive/966a296ac4e4862dee9a571ee412886ca3c61144.zip
on some platforms , e.g. armel:
https://buildd.debian.org/status/fetch.php?pkg=cython&arch=armel&ver=0.25.2~
Ran into it while building a package for Debian
==
FAIL: annotate_html ()
Doctest: annotate_html
--
Traceback (most recent call last):
File "/usr/lib/python3.5/
On Thu, 11 Aug 2016, Yaroslav Halchenko wrote:
> On Wed, 10 Aug 2016, Robert Bradshaw wrote:
> > Is this a change from 0.24? Do you have any s390x hardware that we
> > could test on?
> if anything it is a "change" from 0.23.4+git4-g7eed8d8-2 ... but the
> thi
On Wed, 10 Aug 2016, Robert Bradshaw wrote:
> Is this a change from 0.24? Do you have any s390x hardware that we
> could test on?
if anything it is a "change" from 0.23.4+git4-g7eed8d8-2 ... but the
thing is that since my email Jakub Wilk reported that he hasn't
observed this failure while build
Dear Cython ppl,
Didn't spot any obvious commit/log since 0.24.1 so decided just to report:
full build log:
https://buildd.debian.org/status/fetch.php?pkg=cython&arch=s390x&ver=0.24.1-1&stamp=1470118175
1 test has failed on s390x (only). Quick resolution would help to
assure cython's healthy sta
On Fri, 12 Feb 2016, Stefan Behnel wrote:
> >> ==
> >> FAIL: runTest (__main__.EndToEndTest)
> >> End-to-end asyncio_generators
> >> --
> >> Traceback (most recen
On Wed, 23 Sep 2015, Yaroslav Halchenko wrote:
> On Tue, 22 Sep 2015, Stefan Behnel wrote:
> > > Expected:
> > > -4294967295
> > > Got:
> > > 1
> > I cannot reproduce this locally (even tried a 32bit docker container), so I
> > blin
On Tue, 22 Sep 2015, Stefan Behnel wrote:
> > Expected:
> > -4294967295
> > Got:
> > 1
> I cannot reproduce this locally (even tried a 32bit docker container), so I
> blindly changed a couple of minor things in that branch. Could you give it
> another try?
> If that didn't help, here is
was reported in Debian against 0.23.2 so tried blindly freshier snapshot
from 0.23.x branch and that one is no go too:
==
FAIL: large_nums (line 95) (ct_DEF.__test__)
Doctest: ct_DEF.__test__.large_nums (line 95)
-
FWIW -- uploaded to Debian sid.
0.21.0 experienced some issues during tests on some exotic platforms but
probably not due to cython's issues (tried manually on sparc -- built
fine):
https://buildd.debian.org/status/package.php?p=cython&suite=unstable
Cheers and thanks for keeping Cython going stro
On Wed, 10 Sep 2014, Stefan Behnel wrote:
> on behalf of the Cython dev team, I'm pleased to announce the release of
> Cython 0.21, a major feature release. Thanks everyone who contributed code,
> documentation improvements, test feedback, bug reports and/or otherwise
> helpful insights for this
On Sat, 11 Oct 2014, Stefan Behnel wrote:
> Yaroslav Halchenko schrieb am 11.10.2014 um 16:18:
> > On Wed, 10 Sep 2014, Stefan Behnel wrote:
> >> on behalf of the Cython dev team, I'm pleased to announce the release of
> >> Cython 0.21, a major feature release.
On Wed, 10 Sep 2014, Stefan Behnel wrote:
> Hi all,
> on behalf of the Cython dev team, I'm pleased to announce the release of
> Cython 0.21, a major feature release. Thanks everyone who contributed code,
> documentation improvements, test feedback, bug reports and/or otherwise
> helpful insights
On Fri, 10 Oct 2014, Stefan Behnel wrote:
> Hi,
> thanks for the feedback.
> Yaroslav Halchenko schrieb am 08.10.2014 um 16:23:
> > while preparing build for Debian I ran into good old (never got feedback
> > to my analysis done in Jul/Aug, thread &
congrats!
while preparing build for Debian I ran into good old (never got feedback
to my analysis done in Jul/Aug, thread "Cython bugfix release")
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
-
unc(self, *args, **kwargs)
File
"/tmp/buildd/cython-0.20.2/build/lib.linux-x86_64-2.7-pydebug/Cython/Debugger/Tests/test_libcython_in_gdb.py",
line 72, in read_var
result = gdb.parse_and_eval('$cy_cvalue("%s")' % varname)
error: Error occurred in Python convenie
Python command: 'FakeRepr' object has no attribute
'__getitem__'
MORE
> On 21.07.2014 19:46, Robert Bradshaw wrote:
> > I wasn't able to reproduce this myself, which is why I haven't done
> > anything about it yet...
> > On Sat, J
while trying to re-test Debian package build, in an interactive shell, I
get cython test stuck at:
...
Doctest: buffmt.__test__.wrongsize ... ok
runTest (__main__.EndToEndTest)
End-to-end basic_cythonize ... ok
runTest (__main__.EndToEndTest)
End-to-end basic_distutils ... ok
runTest (__main__.End
that was quite an underwhelming response, now it is "official"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755340
and I haven't had yet a chance to recheck master... anyone has a clue
before I start digging?
On Thu, 19 Jun 2014, Yaroslav Halchenko wrote:
> and the sam
ordinal not in range(128)
--
Ran 8348 tests in 2674.102s
On Wed, 18 Jun 2014, Yaroslav Halchenko wrote:
> FWIW -- 0.20.2 was just uploaded to Debian sid, thus should be available
> to Debian folks soon too
> while trying 0.20.1 across debi
FWIW -- 0.20.2 was just uploaded to Debian sid, thus should be available
to Debian folks soon too
while trying 0.20.1 across debian/ubuntus I ran into this failure
==
ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
On Thu, 20 Dec 2012, Robert Bradshaw wrote:
> > git rev-parse HEAD
> > might be a better choice for this purpose
> > would you accept such a fix/PR ?
> Yes, please send us a fix. (This was written right when we were moving
> to git, before we knew it well.)
apparently I did! ;)
https://githu
On Fri, 14 Dec 2012, Stefan Behnel wrote:
> Yaroslav Halchenko, 03.12.2012 17:23:
> > shouldn't there be
> > http://wiki.cython.org/ReleaseNotes-0.17.2
> > ? ;-)
> You can copy it over from
> https://github.com/cython/cython/blob/0.17/CHANGES.rst
> if you
On Mon, 10 Dec 2012, Stefan Behnel wrote:
> >> so how to make it 'effective'?
> > no hints from the experts? ;)
> Usually, running gc.collect() after this kind of test (i.e. as part of the
> doctest) is a good way to provoke a crash in time.
wasn't it obvious ? ;-) Thanks!
https://github.com
On Wed, 05 Dec 2012, Yaroslav Halchenko wrote:
> On Wed, 05 Dec 2012, mark florisson wrote:
> > > Thanks, I merged it.
> > It'd be nice if you could add this as a testcase in the tests/run
> > directory as a "don't segfault" kind of test.
> I w
On Wed, 05 Dec 2012, mark florisson wrote:
> > Thanks, I merged it.
> It'd be nice if you could add this as a testcase in the tests/run
> directory as a "don't segfault" kind of test.
I would be happy to extend the test battery but my blunt attempt failed,
i.e. the test doesn't cause the failure
ithub.com/cython/cython/commit/d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5
>-Brad
>On Mon, Dec 3, 2012 at 1:10 PM, Yaroslav Halchenko
><[3]li...@onerussian.com> wrote:
> reproduced with cython 0.17.2 (+ few post release fixes), originally
> detected/reported [1] with �0.17.1 on Debia
pardon the initial absence of subject
On Mon, 03 Dec 2012, Yaroslav Halchenko wrote:
> reproduced with cython 0.17.2 (+ few post release fixes), originally
> detected/reported [1] with 0.17.1 on Debian systems using debug build of
> Python:
> $> python-dbg -c 'im
reproduced with cython 0.17.2 (+ few post release fixes), originally
detected/reported [1] with 0.17.1 on Debian systems using debug build of
Python:
$> python-dbg -c 'import pyximport as pi; pi.install(); import weakfail;
s=weakfail.foo(42)'
congrats!
please do not forget to push git tag for 0.17.2 ;)
On Tue, 20 Nov 2012, Stefan Behnel wrote:
> Hi everyone,
> I'm happy to announce the release of Cython 0.17.2. This is a (mostly) bug
> fix release for the stable 0.17 release series.
> http://pypi.python.org/pypi/Cython/0.17.2
> D
shouldn't there be
http://wiki.cython.org/ReleaseNotes-0.17.2
? ;-)
> Complete changelog:
> 0.17.2 (2012-11-20)
> ===
> Features added
> --
> * ``cythonize()`` gained a best effort compile mode that can be used to
> simply ignore .py files that fail to compile.
>
On Wed, 26 Sep 2012, Stefan Behnel wrote:
> http://wiki.cython.org/ReleaseNotes-0.17.1
and a regular contribution:
http://wiki.cython.org/ReleaseHistory
references only 0.17 for me
;-)
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth Colle
On Tue, 25 Sep 2012, Stefan Behnel wrote:
> > Any chance we can tag the official 0.17 release in Github as well?
> BTW, do we use lightweight tags or annotated tags in git? And why?
you should use annotated -a (and/or signed -s, which are annotated) tags
you do not use annotated tags:
$> git de
On Sat, 01 Sep 2012, Stefan Behnel wrote:
> Release notes: http://wiki.cython.org/ReleaseNotes-0.17
http://wiki.cython.org/ReleaseHistory
references only 0.16 for me
;-)
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore H
FWIW -- this beta builds/tests ok across nearly all Debian ports but 4
where process unexpectedly terminates for no obvious reason (it
built/tested just fine on my local sparc box):
https://buildd.debian.org/status/package.php?p=cython&suite=experimental
some time I will check WTF (memory? etc) on
congrats!
my not so wild but still a guess that 0.17b3 corresponds to
5b0e8f8b96e353ac6d12d54f86babee9ff6f1bf8 git commit (never know for sure
if there is no tag :-P )? ;)
On Thu, 23 Aug 2012, Stefan Behnel wrote:
> Hello everyone,
> on behalf of the Cython project team, I'm proud to announce
queeze-gdb7.2-Debugger-tests-output.txt
On Fri, 10 Aug 2012, Yaroslav Halchenko wrote:
> > > Is that the expected behaviour? Or is there just something missing in the
> > > build server setup, maybe something wrong with the gdb Python plugin? It
> > > looks like it
On Fri, 10 Aug 2012, mark florisson wrote:
> > Is that the expected behaviour? Or is there just something missing in the
> > build server setup, maybe something wrong with the gdb Python plugin? It
> > looks like it's doing something, though...
> IIRC, it parses the gdb version to match against g
On Thu, 09 Aug 2012, Stefan Behnel wrote:
> > Is it bad to release something that doesn't pass the entire test suite
> > on some system?
> Given that we already made tons of releases without even knowing that
> they'd fail on some systems, I'd say no. :)
FWIW -- some time ago 0.15.1 build/passe
FWIW -- just double checked -- tests pass (of current master) just
fine on an i386 Debian system.
On Thu, 09 Aug 2012, Yaroslav Halchenko wrote:
> On Thu, 09 Aug 2012, Stefan Behnel wrote:
> > > I thought the 32 bit issue was resolved? You pushed a fix and I fixed
> > > som
d I have not uploaded any new
revision to Debian since 0.17 beta1.
,---
| Date: Thu, 2 Aug 2012 10:30:32 -0400
| From: Yaroslav Halchenko
| To: cython-devel@python.org
| Subject: Re: [Cython] [cython-users] Re: Cython 0.17 beta 1 released
|
|
| On Wed, 01 Aug 2012, mark florisson wrote:
| > Tha
On Thu, 02 Aug 2012, Stefan Behnel wrote:
> > just a side-note -- I didn't know that StrictVersion doesn't play nicely
> > with LooseVersion to any degree:
> > $> python -c 'from distutils.version import LooseVersion as LV,
> > StrictVersion as SV; print SV("0.17") > LV("0.18")'
> > True
> >
On Thu, 02 Aug 2012, Stefan Behnel wrote:
> Bradley M. Froehle, 01.08.2012 18:35:
> > Yes, this versioning has also impacted mpi4py which had to add some pretty
> > ugly code in setup.py to work around it:
> > https://code.google.com/p/mpi4py/source/detail?r=841e9df
> >> I am not sure what is
On Wed, 01 Aug 2012, mark florisson wrote:
> Thanks for the fix. I also pushed a fix for one more test numpy_test
> related to fused types dispatching. That passes all tests for me on 32
> bit linux.
> > Yaroslav, could you give it a try on the Debian build servers?
FWIW -- 0.16rc1-550-g8880c78
ing tags accordingly)?
[1] http://www.python.org/dev/peps/pep-0386/
[2] http://bugs.debian.org/683133
On Wed, 01 Aug 2012, Yaroslav Halchenko wrote:
> ok, the output of running
> OPT="-g -O0" /usr/bin/python runtests.py -vv --no-cleanup 2>&1 | tee
> ../0.16rc1-54
nerussian.com/tmp/0.16rc1-547-g68811fa-tests-output.txt.gz
especially interesting are failures like:
ValueError: Buffer dtype mismatch, expected 'char' but got 'char' in
'UnpackedStruct.a'
;-)
or may be I should have invoked tests anyhow differently (build manu
sorry about the delay -- was not monitoring the ML tight enough ;)
So it is the
commit 8443607d7dffc7c8443d70036e0cce6aaa9c26e2
Author: Stefan Behnel
Date: Tue Jul 31 21:49:20 2012 +0200
determine buffer typegroup of integer dtypes based on signedness at C
compile time
...
I pulled curre
On Wed, 25 Jul 2012, Robert Bradshaw wrote:
> > ultimate suffix under assumption that it would not change (also removed
> > unused
> > _code_cache) (it came out a bit longer simply due to me adding helper
> > function
> > _get_build_extension() to avoid duplication):
> Looks good. Thanks. File
On Wed, 25 Jul 2012, Robert Bradshaw wrote:
> > module = imp.load_dynamic(module_name, module_path)
> > arg_list = [kwds[arg] for arg in arg_names]
> Compiled modules can persist between sessions as well.
yeah -- figured it down also while working on another version of this
trivial pa
ches?
+module_path = os.path.join(lib_dir,
build_extension.get_ext_filename(module_name))
+_code_cache[module_name] = module_path
module = imp.load_dynamic(module_name, module_path)
arg_list = [kwds[arg] for arg in arg_names]
On Wed, 25 Jul 2012, Yaroslav Halchenko wrote:
&
On Wed, 25 Jul 2012, Robert Bradshaw wrote:
> One essential feature of cython.inline(...) is that if the code has
> already been compiled (and loaded) it should return very fast. This
> would seem to add significant overhead.
that is what was my concern also with such an approach... I am not s
NB Sorry for a lengthy reply -- more like notes for myself I guess ;)
Short story -- imp.get_suffixes()[0] != get_config_var('SO')
on Debian multiarch sid
Perspective patch is at the bottom.
On Wed, 25 Jul 2012, Stefan Behnel wrote:
> > anything familiar? (I see PY3 fix bf7981fb37b19f08a
Congrats on the beta-release! While testing an updated debian package
for cython I have ran into failures with Python 3.2.3 (default, Jul 13 2012,
21:02:37) [GCC 4.7.1] (complete log:
http://neuro.debian.net/_files/_buildlogs/cython/0.17~beta1/cython_0.17~beta1-1_amd64.build)
anything familiar? (
On Tue, 17 Jul 2012, Yaroslav Halchenko wrote:
> I have tested on a sparc box and current master seems to not show this
> particular problem (see below though) -- does anyone remember this
> particular issue and commit which fixed it?
I am sorry -- I got lost among architectures and w
Hi everyone!
1. uploaded 0.16 to Debian experimental... many platforms fail with smth
like
,--
| ==
| FAIL: Doctest: memslice.__test__.test_padded_structs
| --
|
please pardon my sloppy cut/paste which ruined the subject line in the
original post ;) So the topic is:
On Mon, 02 Jul 2012, Yaroslav Halchenko wrote:
> I was thinking about updating Debian package for cython 0.16 but ran into
> the failing unittests so decided first to check with e
I was thinking about updating Debian package for cython 0.16 but ran into
the failing unittests so decided first to check with experts: anything obvious
which comes to mind from seeing those?
...
compiling (c) and running sequential_parallel ... sequential_parallel.c: In
function '__pyx_pf_19sequ
most grateful to ye landlubbers reports o' sad tails o' bugs.
> Fair winds!
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
__
before assignment
first and it is logical to require initialization. Thanks!
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
___
lenB
cnp.ndarray[object, ndim=1] tracksA32
...
# some code ... cut
if track_len > longest_track_lenA:
longest_track_lenA = track_len
--
=--=
Keep in touch
-=
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
confirming now -- built/tested fine manually on s390, uploaded, and now
built across nearly all (few still building/testing) archs:
https://buildd.debian.org/pkg.cgi?pkg=cython
On Fri, 18 Feb 2011, Yaroslav Halchenko wrote:
> > >> We are very near to be crystal clear...
> > >
ou guys -- I do not think there is anything in
Debian policy/guidelines about cleaning up TMPDIR.
I, personally, would have preferred them being cleaned up.
--
=--=
Keep in touch www.onerussian.com
Yaroslav
s... I will let you
know of cause ;)
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
___
cython-devel mailing
e.g.
FAIL: Doctest: c_int_types_T255
FAIL: Doctest: c_int_types_T255.__test__.test_char (line 90)
FAIL: Doctest: dictintindex.__test__.test_get_char_neg (line 1)
otherwise -- amazingly nice ;-)
On Thu, 17 Feb 2011, Yaroslav Halchenko wrote:
> > > | AssertionError
> > > `---
&g
-=
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
70 matches
Mail list logo
