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

doesn't work with python3 #6

Closed
hasufell opened this issue Apr 4, 2015 · 4 comments
Closed

doesn't work with python3 #6

hasufell opened this issue Apr 4, 2015 · 4 comments

Comments

@hasufell
Copy link

hasufell commented Apr 4, 2015

Old pygame (at least the 1.9.2 pre-releases) compiled fine with python3. pygame_sdl2 currently doesn't. The first error I get is invalid syntax for "print".

@renpytom
Copy link
Member

renpytom commented Apr 4, 2015

This is correct, and something that needs to be addressed relatively soon.

@renpytom
Copy link
Member

renpytom commented Apr 4, 2015

I've addressed this. The current HEAD branch should be able to build and run on python3. Please let me know if you have problems - those are now proper bugs, rather than something we didn't get to.

@renpytom renpytom closed this as completed Apr 8, 2015
@Elinvention
Copy link

$ python3 setup.py install
pygame_sdl2.error is out of date.
pygame_sdl2.color is out of date.
pygame_sdl2.controller is out of date.
pygame_sdl2.rect is out of date.
warning: src/pygame_sdl2/rect.pyx:402:8: Unreachable code
pygame_sdl2.rwobject is out of date.
pygame_sdl2.surface is out of date.

Error compiling Cython file:
------------------------------------------------------------
...
                self.surface.pitch)

        self.unlock()

    def set_colorkey(self, color, flags=0):
        print color
             ^
------------------------------------------------------------

src/pygame_sdl2/surface.pyx:381:14: Syntax error in simple statement list

Command '['cython', '-3', '-Iinclude', '-Igen3', '-a', 'src/pygame_sdl2/surface.pyx', '-o', 'gen3/pygame_sdl2.surface.c']' returned non-zero exit status 1

Should I open a new issue?

@renpytom
Copy link
Member

No need. I just fixed it with acc3178.

If it happens again, opening a new issue to track it would be good, as I can close it as part of the command. Hopefully it won't happen again, though.

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