Re: [Cython] build failure on windows with 0.21b2 windows py27 x64

2014-09-06 Thread Dirk Rothe 
On Fri, 05 Sep 2014 20:47:47 +0200, Stefan Behnel   
wrote:



Dirk Rothe schrieb am 01.09.2014 um 12:25:

I've also tested with windows+py27+x64 and I get the same errors;

configobj.c(42437) : error C2121: '#' : invalid character : possibly  
the

result of a macro expansion
configobj.c(42437) : error C2146: syntax error : missing ')' before
identifier 'ifdef'
configobj.c(42437) : error C2121: '#' : invalid character : possibly  
the

result of a macro expansion
configobj.c(42439) : error C2059: syntax error : 'else'
configobj.c(42449) : error C2059: syntax error : '}'
configobj.c(42463) : error C2121: '#' : invalid character : possibly  
the

result of a macro expansion
configobj.c(42463) : error C2121: '#' : invalid character : possibly  
the

result of a macro expansion
error: command '"C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\BIN\amd64\cl.exe"' failed with exit status 2


Here we go, I have annotated the start/end with line numbers:

#if CYTHON_COMPILING_IN_CPYTHON ## Line 42431
static CYTHON_INLINE PyObject* __Pyx_PyObject_CallOneArg(PyObject *func,
PyObject *arg) {
if (likely(PyCFunction_Check(func)
#ifdef __Pyx_CyFunction_USED
|| PyObject_TypeCheck(func, __pyx_CyFunctionType)
#endif
) && likely(PyCFunction_GET_FLAGS(func) & METH_O)) {
return __Pyx_PyObject_CallMethO(func, arg);
} else {
PyObject *result;
PyObject *args = PyTuple_New(1);
if (unlikely(!args)) return NULL;
[...]


Thanks. My guess is that the macro nesting is a bit too heavy for MSVC
here. I pushed a change to the master branch that simplifies it. Could  
you

give it another try?

https://github.com/cython/cython/commit/2a1f74aac867fee81e2ddf073f16519f3f454bac


Thanks Stefan! The latest Trunk works fine for me now.

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

Re: [Cython] preparing a release candidate, pending issues

2014-09-06 Thread Robert Bradshaw 
On Fri, Sep 5, 2014 at 12:39 PM, Stefan Behnel  wrote:
> Hi,
>
> current master looks good enough to plan for a release candidate next week.
> There are only a couple of pending issues that I'm aware of that may or may
> not get looked into for the release.
>
> One thing is cygdb and its tests - are they working again? They seem to
> work for me, but I don't know what the last status was there. Given how
> long they must have been broken, it doesn't look all too critical, though.
>
>
> This one should be resolved now:
>
> "build failure on windows with 0.21b2 windows py27 x64"
> http://thread.gmane.org/gmane.comp.python.cython.devel/15424

+1, though I don't have any ideas here.

> This isn't, but the solution isn't currently obvious (and I think it can
> wait until the first bugfix release if we can't find a fix in time):
>
> "Buffer dtype mismatch error"
> http://thread.gmane.org/gmane.comp.python.cython.user/11603

The only solution I can think of, short of fixing NumPy, is adding a
directive to not do the check.

> These are open, but don't feel like they should block the release:
>
> "error LNK2001: unresolved external symbol PyInit_init"
> http://thread.gmane.org/gmane.comp.python.cython.devel/15392/focus=15415
>
> "Memory leak with vector of memoryviews"
> http://thread.gmane.org/gmane.comp.python.cython.user/11704/focus=11705
>
> "how to have hashable extension types in pure python mode ? (__eq__ error)"
> http://thread.gmane.org/gmane.comp.python.cython.user/11731/focus=11732

Agreed.

> This isn't finished but is a new feature which can wait:
>
> "Automatic conversion with fixed-size C arrays"
> https://github.com/cython/cython/pull/308

Yeah, this isn't done yet.

> This hasn't lead anywhere, apparently, but can wait as well:
>
> "OpenMP thread private variable not recognized (bug report + discussion)"
> http://thread.gmane.org/gmane.comp.python.cython.devel/15382
>
>
> So, nothing critical, but I might have forgotten something. If nothing else
> comes up, I'll just wait a couple of more days and then start preparing RC
> and final release.

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

Re: [Cython] Compiler crash in RemoveUnreachableCode

2014-09-06 Thread Stefan Behnel 
Andriy Kornatskyy schrieb am 19.01.2014 um 21:00:
> The cython compiler crash report below. Steps to reproduce:
> 
> 1. virtualenv env
> 2. env/bin/easy_install cython
> 3. env/bin/easy_install wheezy.http
> 
> The wheezy.http has dependency on wheezy.core. If I install those two 
> packages separately there is no error, only if through dependencies.

I tried "pip install wheezy.http" instead of "easy_install wheezy.http" and
it works as expected. This sounds like a good work-around to me.

Stefan

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