Am I still allowed to do bug fixing today?

Judging by the official rules I'd say 'no' ... but some other comments here suggest 'yes' ...
How is this officially handled?

(log in to comment)

Comments

If it's a "damn I forgot to uncomment this one line" fix it. If it's "I'll have to rewrite collision handling" best do it after the competition. At least that's my impression of the unwritten rules.
In the UK at least, there's a programme called Scrapheap Challenge, in which teams get something like 8 hours to build a machine from scrap. Then, the next day, before the machines compete, there's an hour's "tinkering time". Sometimes teams use this to paint their machine, sometimes just to ensure it's running smoothly, and occasionally to actually get it finished, which always seems to get glossed over in the programme.

But the point is, you can't have a competition unless the competitors' machines are working.

That's just a piece of philosophy. I don't know how it relates to the actual rules.
Thank you for your answers, cyhawk and mauve.

My bugs definitely were of the "damn I forgot" kind (like calling surface.convert() but then going ahead using the un-converted original surface anyway ... ). Though I have to admit they weren't any game breaking bugs either - so the game could have entered the competition without them.

Well, in the end I did upload a new version, but added a comment explaining that I fixed a few bugs after the deadline. This way, people can decide for themselves which version they want to rate for the contest.
The consensus seems to be that minor bug fixes are acceptable. Sometimes things only show up when 50 people start hammering on your game, and it would be mean-spirited to make a game miss out because of something like that.
Indeed. It's just not time for adding new stuff; that's what the week of PyWeek is for :-)
Stop writing, put your pens down, now make it work for me?