Help for using the PyWeek Challenge Site
- 1. So you want to enter as an individual?
- 2. So you want to enter as a team?
- 3. Editing your personal details
- 4. Don't want an Entry any more?
- 5. Want to change Team Leaders?
- 6. Want to join a team?
- 7. What to do before the challenge starts
- 8. What do do during the challenge
- 9. How to submit your entry
- 10. What to submit as your entry
- 11. When does PyWeek run?
- 12. When can I sign up?
- 13. How do I upload a file?
- 14. How do I post a diary entry?
- 15. What's PyWeek all about?
You should log into the PyWeek site and go to the latest challenge in the sidebar. Then in the the sidebar you should see "Register Entry". Click that and fill out the details. Leave the "Team Members" bit blank.
Once you've done that, your entry will appear under your "Your entries" list.
You may add diary entries and upload files or screenshots to this entry (the latter only once the challenge has started).
This step should be performed by the team leader.
You should log into the PyWeek site and go to the latest challenge in the sidebar. Then in the sidebar you should see "Register Entry". Click that and fill out the details. You may fill in the "Team Members" bit now or come back and edit it later.
Once they've done that, their entry will appear under your "Your entries" list.
You may add diary entries and upload files or screenshots to the team entry (the latter only once the challenge has started).
Only the team leader will be able to manage the team entry (change its name or membership listing).
Once you've logged in use the "Profile" link in the sidebar to change your name, email address or password.
Ask the team leader of that team to add you.
- Make sure you have working versions of the libraries you're going to use.
- Make sure you can build packages to submit as your final submission (if you're going to use py2exe, make sure you know how to use it and that it works).
- If you don't have access to Linux, Windows or a Mac to test on, contact friends, family or other competitors to find someone who is able to test for you.
- Plan on spending at least several hours packaging and testing your packaging.
- Allow time for planning your game (for example 1/5 of the total time)
- Allow time for polishing the game by adding instructions, opening menus, level transition screens, game over screen (for example 1/5 of the total time)
- Upload screenshots and put them in diary entries!
- Hang around in the IRC channel, irc.freenode.net channel #pyweek
Visit your entry's page any time during the challenge and up to 24 hours after the finish to upload your file(s). You may upload as many files as necessary, including screenshots.
The server will become heavily loaded at deadline times. Given that there is an entire 24-hour period in which to upload your files after the challenge finishes there will be no leniency for failure to upload.
Consider the advice at http://www.pygame.org/wiki/distributing
We recommend you download the Skellington 1.9 package and use that as the starting-point for your game.
For this challenge,
- Always use either ZIP or TAR / GZIP to bundle your entry.
- Always use a top-level directory.
- You MUST include a README.txt which at a minimum indicates:
- who wrote the code
- who created the artwork
- how to run the game
- the licence for the game (the Free Software Foundation has a handy page of free software licenses)
- what dependencies need to be installed
- a plug for the challenge is nice :)
- If possible, you should bundle other libs you've used. If it's pure Python, then it may be bundled straight. If not, then consider including the source for the library.
- If your entry is large (greater than 1MB) then you might want to use the pyweek uploader script to upload it, as it will handle bigger uploads better.
PyWeek runs every 6 months in Spring/Autumn. This usually works out to be around the first week of April and September.
Registration for PyWeek opens one month before the challenge start date and continues through until the very end of the week-long challenge.
Yes, you can sign up during the week.
You may only upload a file during the running of the challenge (ie. after the start date). If you wish to upload outside of that time, contact Richard at email@example.com
To upload a file:
- log in,
- select the entry you wish to upload it for in the sidebar,
- select "Upload File" or "Upload Screenshot" in the sidebar, and
- fill out the "Upload a File" form.
See the separate section 9. How to submit your entry for more information about submitting your entry to the site.
To post an entry:
- log in,
- select the entry you wish to post the entry for in the sidebar,
- select "Add Diary Entry" in the sidebar, and
- fill out the form.
Your entry will automatically be listed on the front page of the site.
I created PyWeek after competing in and running several Ludum Dare 48-hour challenges. I had a few problems with the format of that challenge:
- Being over 48 hours meant that you had to focus on the game for most, if not all of the 48 hours. This can be difficult for some of us to organise. Spreading the development over a week is much easier.
- I wanted to be able to collaborate with friends and LD48 is a solo-only challenge.
- There's lots of public-domain or Creative Commons artwork and audio out there that people shouldn't be prevented from using. Also, I suck at both drawing and musical composition :)
The Python-only stipulation was partly as an experiment (to see whether we'd get more games that worked for more people than the LD48 experience) and also as a tool for promoting Python (which I think rocks, a lot).
PyWeek was conceived and originally run by Richard Jones. PyWeek number 1 was run in August 2005.
Pyweek 22-24 were run by Blake O'Hare.
Pyweek 25-26 were run by Daniel Pope.
Various other people have helped out with the website over the years, including Lucio Torre, Juan Martinez, and Lex Toumbourou.
The participation in PyWeek has been pretty steady since the start, with ups and downs depending on how widely the challenge is promoted (or whether I manage to schedule it particularly badly):
The first challenge was announced about 3 months out, and a bunch of people registered that didn't return for the challenge, hence the low number of finished entries. Since then registration has only been opened to new users one month from the start date. This appears to have reduced the number of unused registrations.