Re: [pygame] separating pygame dependent code from general code

Just to weight in, as an old time Python user, new time pygame user. The thing I love the most about Python is it's flexibility. For my first project, I'm still using everything-in-one file: https://github.com/audiodude/Butterfly-Catcher/tree/basic You can always refactor. But if you prefactor, y

Re: [pygame] separating pygame dependent code from general code

Hey, I like the following... mygame/ mygame/run_game.py mygame/mygame/__init__.py mygame/mygame/yourothercode.py mygame/mygame/data I tried to update the skellington after the last pyweek based on bugs... https://bitbucket.org/illume/skellington2011 but there are still a number of improvements

Re: [pygame] separating pygame dependent code from general code

On Tue, Jun 7, 2011 at 9:52 PM, DR0ID wrote: > Hi > > In a library, how would pygame dependent code be separated from general > code? > > Let's say that I write a package named 'mygamepack'. In that package there > are some modules that are only dependent on python (general parts) and there > are

[pygame] separating pygame dependent code from general code

Hi In a library, how would pygame dependent code be separated from general code? Let's say that I write a package named 'mygamepack'. In that package there are some modules that are only dependent on python (general parts) and there are some others using pygame (lib dependent parts). How wou