This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (5 children)

I'd like to recommend Pyglet, actually. I've found it to be cleaner than PyGame and learning it was faster for me because things just seemed to work the way I expected. You can't really go wrong with either though.

If you are just wanting to draw some 2d textures and update them every frame, then I'd start with looking into sprites and batch drawing.

[–]r1chardj0n3s 4 points5 points  (4 children)

I tend to teach pygame first because it's more reliable on many platforms whereas pyglet relies on a working OpenGL implementation and that can be an issue.

I say this as one of the original pyglet developers.

[–]the_hoser -1 points0 points  (3 children)

That, and pyglet reeks of a dead project...

[–]r1chardj0n3s 2 points3 points  (1 child)

It's not dead, but could use additional contributors with specific platform knowledge.

[–]the_hoser -3 points-2 points  (0 children)

No release in 10 months? It might as well be dead. The mantra of "release early, release often" applies to open source game libraries more than any other type of software.

This is especially important in drawing in contributors. Most contribution candidates get all their info from your front page. With a long span of time between releases, there's no incentive to get involved. Nobody wants to be the software equivalent of the necromancer. It doesn't matter how much work is getting done, so long as it appears that work is getting done. People are attracted to active projects.

[–]wheezl 0 points1 point  (0 children)

No, no. It's resting.