A few graphics I've made, I may use them during pyweek, ain't sure, but you can use them: Here

A few graphics I've made, I may use them during pyweek, ain't sure, but you can use them: Here

Something that disappoints me about a lot of entries to PyWeek is that they don't spend the small effort required to have someone else test their game or write a nice README listing how to get the game going: dependencies, which file to run, the controls, etc.

A recurring issue we have in the challenge is that a lot of entries aren't runnable on some people's computers, for various reasons (can be as simple as documentation). We have the additional problem that non-game-hacker types come along and download a selection of games only to find they don't work (and then promptly give up thinking what a terrible platform we must be working with).

The rules currently state that entries should include "instructions about how to run the entry" and I'm considering changing this to must. I think it's that important that if you can't get a game to run* then that game should be a disqualification vote.

The challenge is a week long. I have trouble believing that people couldn't find some time to have friend(s) (including us other challengers) try out the game during that week.

*: note that I don't care whether the game is "complete" ... just that it should be possible for a 3rd party to get the game working.

I'd really like to use OpenGL2.0, what are my best options for this?

From what I can see, OpenGL-ctypes doesn't yet provide OpenGL2.0.

I've had someone ask, so here's the themes that were available for voting on for the first three challenges:

Pyweek #1:

• Life
• Time
• Motion
• Velocity
• Power

Pyweek #2:

• Someone else's trash
• A fraction too much friction
• Mind the gap
• Doorways
• It runs on steam!

Pyweek #3:

• Pick a card, any card
• Watch me pull a rabbit from this hat
• Sawn in half
• Spoon bending
• The Disappearing Act

(Winning theme highlighted)

Looking back on Pyweek3, I got stuck on trying to fix just one bug rather than cutting my losses and moving on. I'm not making that mistake again - I'm keeping it all very simple.

The theme for the Pyweek 4 warmup week is "One is enough". The "official" deadline is next Friday, March 23rd, 14:00 GMT, but the warmup isn't really about deadlines, so don't worry if you miss it. Happy hacking!

Announcing the Pyweek 4 warmup week.

The Pyweek 4 warmup week will start tomorrow at 14:00 GMT (that's 2:00 PM), when I will announce a theme here on this thread. Participants will have until next Friday to work on their games based on that theme, but please, don't stress out. Save it for Pyweek! You don't even have to finish a game, and you don't have to use the whole week. Just use your Saturday afternoon, or maybe a couple of hours each day, whatever you like. The whole idea is just to get warmed up a bit before the actual competition, which of course will be blood, sweat and tears all over. ;-)

I will announce the theme tomorrow. I have a list of different themes and I will probably just pick one out at random. If you like, you can suggest your own theme, and I'll include it in the theme lottery.

Panda3d is a free 3d game engine with python bindings. It's windows only. I doubt it would be allowed, but what's everyone elses thoughts. Do windows only solutions get graded harshly.

Hey, My team is wanting to build a Mario3 style game this time-around. We've got our coded and music/sfx covered quite well at this point - but we could use as many people as possible on tiles/sprites/levels. Reply here if interested. Or maybe I'll be in #pyweek. Phil