Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python 3.3 + Cython 20.1 build failure #61

Open
popham opened this issue Feb 22, 2014 · 2 comments
Open

Python 3.3 + Cython 20.1 build failure #61

popham opened this issue Feb 22, 2014 · 2 comments

Comments

@popham
Copy link

popham commented Feb 22, 2014

I've got a failing build on an Archlinux 64-bit box with Python3.3 installed from source:

    Error compiling Cython file:
    ------------------------------------------------------------
    ...
            :Exceptions:
                - `ValueError`: The value could not be parsed.
            """
            cdef sockaddr_in * sin
            cdef sockaddr_in6 *sin6
            cdef sockaddr_un * sun
                ^
    ------------------------------------------------------------

    coro/socket.pyx:990:13: 'sockaddr_un' is not a type identifier

I've traced the problem to the Cython compiler comparing UNAME_SYSNAME against "Linux" with one encoded as bytes and the other as a unicode string in socket.pxd:

    cdef extern from "sys/un.h":
        IF UNAME_SYSNAME == "Linux":  # I'm broken
            cdef struct sockaddr_un:
                short sun_family
                char sun_path[104]
        ELSE:
            pass

I'm not sure if this is a bug here or upstream. I think the official Cython string philosophy may require a -3 flag to the Cython build in my use-case.

@markpeek
Copy link
Member

I looked at this a little bit over the weekend. While I can get past the above issue with:
IF UNAME_SYSNAME == u"Linux":
it really is the more general issue of support Python 3.x. I'm going to talk with some of the other committers to see what we can do to support it.

@cjrh
Copy link

cjrh commented Mar 28, 2016

Seems like #76 is a duplicate of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants