-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bunch of additions #4
Conversation
This reverts commit 9921201.
Also curious, what version of python are you running this in? I'm on OSX and generally run in pygame 1.9.1 with python2.6 but i'm trying to build 1.9.1 for 2.7.2 and am having issues |
Thanks for checking out the revisions! I built it successfully in Python 2.7.1 + pygame 1.9.1 on Linux. I'll try to get jbttn to comment on those commits you're wondering about. You might be able to get it to build without those commits. |
I used python 2.6.1 I believe, whatever comes with 10.6 with the latest stable version of pygame (1.9.1) 94ef21b was an error, 3e5d24f fixes the error russ made and inserts the line I intended to be there. The reason for the changes was that in the original code I was getting some sort of infinite recursion which happened whenever your custom WorkingSingle function was called, increasing pythons maximum recursion limit didn't help at all so I had to figure something else out. Googling around I found this thread on the GroupSingle memory leak problem: I took a look at the code the poster provided in the "pygame_memleak2.py" file and applied the same technique on this projects code. Instead of using GroupSingle I used Group and used the empty() call where necessary which you can see in 10da8f7, this fixed the crash issue I was experiencing. It seemed to work on other platforms as well so we just got rid of the WorkingSingle function. |
ok, sounds good; WorkingSingle has seemed to be working fine for me though how did you detect the recursion? I'll have to work on getting pygame installed, I have python 2.7 installed with homebrew but still have 2.6. Trying to build it by hand for 2.7 didn't work at all so I'll just use the installer. |
The game crashed with the error whenever trying to play on OSX 10.6.7, it was weird becuase it only happened on this platform but worked with everything else, heres a snip of the error: Traceback (most recent call last): [The pygame.sprite.Group.add() call would then repeat for a long while] File "pyrunner.py", line 522, in add |
Hm odd used to work fine for me on 10.6. Ok, let me get pygame reinstalled and take a look at this |
Looks like I have to install 1.9.2 on my system unless I can get a build to work, 1.9.1 installer wouldn't work |
Ok I can confirm I'm having the recursion error as well |
Really like the new laser sound though |
perhaps you guys could check this issue out that needs fixing: #5 |
Thanks for pulling in our changes! |
Changes: