Working on Learning required Libs

So i've been trying to figure out what libs to use and to get the package ready for playing.. you know creating the exe for windows and such.
  • installing required libs                                [check]
  • checking if py2exe works with required libs  [check]
  • getting the dist scripts ready                      [check] 
as usual i have been thinking about a concept that will incorporate all the themes put for voting :) .. i know.. sounds ridiculous.. but has worked pretty well so far so.. trying to do it again.. :D    

(log in to comment)


Seems like a good idea to finish such things *before* the challenge. Thanks for enlightening me! :)

BTW what are the "dist scripts"?

What libs will you be using?
The Pyweek skellington (and some other more heavyweight project templates which do some of the same things, such as Porygon) include various scripts for packaging your game for distribution. Making sure you've got a working, automated process for building releases, including standalone executables for various platforms and so on, can save valuable effort during crunch time on the last day ;)
It wouldn't be a terrible time to have a look at, or some other VC tutorial ;)
@wisty .. i thought everybody was just going to use for code repo.. hginit looks pretty cool.
@gizmo can host Mercurial :-)
oops... didn't know that.. :) 
btw.. did you guys know about pyinstaller??
sounds like it could be very useful.. trying to test it out now..    
The skellington structure seems really cool, with uploads scripts and all.

Since I don't have the time to learn pyglet (which seems lika great API to know), I'm gonna go for pygame this time. I usually use py2exe for the windows platform, but for ubuntu (which is my main OS at home and thus game development environment) I usually build a small "install_dep"-script in the root of the app, that does the appropriate "sudo apt-get"-commands.
.. and I use bzr + Launchpad for backup of source.
@objarni I think most Linux users would prefer they sudo your script rather than have it do the sudo.
richard - thanks for that hint.

When sudo'ing inside the script, the user gets a "password"-prompt, so technically there is no security risc or anything.
@objarni only if they've not configured sudo to not require a password
richard - ah didn't know that was possible. I guess I'd like to print some message if the user does not have sudo-previlegues, something like "You have to run this script with sudo - sudo install_dep.", if the user forgets.