Re: beginning GSOC preparations: was Re: [pygame] Thank You

Biggest problems I could see are in two areas, misinterpretation and structural. Depending on the filesystem, and current hardware setup, some of the files may still be being written to disk(say a network drive or during lots of other writes) when the tests are run. In terms of misinterepretation,

Re: beginning GSOC preparations: was Re: [pygame] Thank You

We could add it as an optional 'test' command option. Lenard René Dudfield wrote: That reminds me... should we make the tests run at the end of an install automatically? Should make it easier for people to figure out if there are problems... but might cause it's own problems too. On Thu,

Re: beginning GSOC preparations: was Re: [pygame] Thank You

That reminds me... should we make the tests run at the end of an install automatically? Should make it easier for people to figure out if there are problems... but might cause it's own problems too. On Thu, Apr 23, 2009 at 2:39 PM, Lenard Lindstrom wrote: > One last step, run the unit test s

Re: beginning GSOC preparations: was Re: [pygame] Thank You

One last step, run the unit test suite. I will only take a few minutes (still under construction). python -c "import pygame.tests.go" Tyler Laing wrote: And that works! Fantastic, thank you gentlemen for all the assistance. Much appreciated. -Tyler On Wed, Apr 22, 2009 at 9:22 PM, Lenard L

Re: beginning GSOC preparations: was Re: [pygame] Thank You

And that works! Fantastic, thank you gentlemen for all the assistance. Much appreciated. -Tyler On Wed, Apr 22, 2009 at 9:22 PM, Lenard Lindstrom wrote: > python setup.py build --compiler=mingw32 install > > setup.py allows multiple steps, like build and install, to be listed in one > command.

Re: beginning GSOC preparations: was Re: [pygame] Thank You

python setup.py build --compiler=mingw32 install setup.py allows multiple steps, like build and install, to be listed in one command. The install option doesn't recognize the --compiler option, but the build option. The build option, which install uses when need, does recognize --compiler. I o

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Thanks guys, I've got it all working now. The second step with: python setup.py --compiler=mingw32 install throws an error, saying that --compiler is not recognized. -Tyler On Wed, Apr 22, 2009 at 8:40 PM, Lenard Lindstrom wrote: > This would be from a patch msys_build_deps.py makes to work a

Re: [pygame] C/C++ and Python

Psyco working? It looks like it might not work on 64 bit machines. The Psyco Intro says Psyco "only runs on Intel 386-compatible processors", and Wikipedia says that's 32 bit. I could be wrong, but that might mean it won't work. Regardless of wha

Re: beginning GSOC preparations: was Re: [pygame] Thank You

This would be from a patch msys_build_deps.py makes to work around freetypes being built in strict mode, that is, no extensions like 'inline'. The MinGW stdlib.h has an inlined function, causing the compile to fail. I believe René used a different fix from mine. So to disable mine edit msys_bui

Re: beginning GSOC preparations: was Re: [pygame] Thank You

You can run everything from the Msys console, which is more Unix like. In Msys a Windows drive letter translates to a top level Msys directory of the same name. So C:\windows\system32 becomes /c/windows/system32. Add the Python root directory to the executable path and everything should work:

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Okay, it compiled both SDL and zlib, but it failed on freetype. Here's the error message: from freetype-2.3.7/src/base/ftsysem.c:29: ../include/stdlib.h:317: error: syntax error before "double" Right now I'm compiling the rest, so we'll see if there's any other errors. -Tyler On Wed, Apr 22, 2

Re: [pygame] C/C++ and Python

I ment Pyglet or PyOpenGL --- On Mon, 4/20/09, Casey Duncan wrote: From: Casey Duncan Subject: Re: [pygame] C/C++ and Python To: pygame-users@seul.org Date: Monday, April 20, 2009, 9:46 PM fwiw, with pyglet you don't need PyOpenGL, it has it's own OpenGL wrapper with some nice abstractions bu

Re: [pygame] C/C++ and Python

I can't get psyco working - I have a 64 bit computer --- On Tue, 4/21/09, Knapp wrote: > Combined with things lke psyco, and numpy - you can avoid doing a lot of > things in C.

Re: beginning GSOC preparations: was Re: [pygame] Thank You

hi, try this: python msys_build_deps.py --all then this: python setup.py build --compiler=mingw32 install On Thu, Apr 23, 2009 at 10:18 AM, Tyler Laing wrote: > I'm sorry if I seem dense throughout all of this, XD. Okay, so I take your > package there, unzip it. I copy the pygame source

Re: beginning GSOC preparations: was Re: [pygame] Thank You

I'm sorry if I seem dense throughout all of this, XD. Okay, so I take your package there, unzip it. I copy the pygame source code trunk into there. I then use the windows cmd, and cd into that directory, and run python setup.py --compiler=mingw32 install ? I'm sorry, but you're going to need expli

Re: beginning GSOC preparations: was Re: [pygame] Thank You

hi, try this: http://rene.f0o.com/~rene/pygame_mingw32_compile_pack.zip They are the installers for mingw stuff I last installed on my windows machine to compile pygame. Other people have used those to successfully compile it too... so it should work. Also, if you get the dependency sources tha

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Unfortunately, it doesn't work. Does anyone have a better guide or series of steps to compiling pygame? Those steps should include properly install msys and associated packages. If not, I'll go over and start using the prebuilts. Thanks for the effort Lenard. -Tyler On Wed, Apr 22, 2009 at 2:55 P

Re: [pygame] Porting to Python 3.0 - the python3 branch (Done!)

Well, the aliens.py example runs, so that fullfills the initial requirements outlined in this thread. Porting to Python 3 will continue, but at a more leisurely pace. Again, the branch is in svn, accessible with: svn co svn://seul.org/svn/pygame/branches/python3 Enjoy, Lenard Lenard Linds

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Did you install the Msys autoconf, automake and m4 packages from sourceforge? They are found under the MSYS Supplementary section of the MinGW download page. I suggest using the most recent versions available. Lenard Tyler Laing wrote: Its failing on SDL. I tried running .autogen.sh in the dir

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Its failing on SDL. I tried running .autogen.sh in the directory, and this is what I got. I just made sure all the extra packages had been extracted to where they should be... including the update automake, autoconf and m4 tars. $ ./autogen.sh Generating build information using autoconf This may

Re: [pygame] Porting to Python 3.0 - the python3 branch (Was: pygame for portable python)

Ok, examples/chimp.py now runs from Python 3.1. That just leaves mixer.music and some cleanup. Also I confirmed the python3 branch still compiles for Python 3.0 under Windows XP and the stars.py example runs. Lenard Lenard Lindstrom wrote: I have now added sprite, time and transform to the l

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Which package are you trying to build. Unless the thing crashed completely msys_build_deps.py should have displayed a listing at the end showing where it stalled, that is, it will show which DLL were not installed. The packages taken straight form SVN may not have a .configure file. msys_build_

Re: [pygame] PyGame Website Rewrite

LOL, you nailed it right on the head. On Wed, Apr 22, 2009 at 3:14 PM, Devon Scott-Tunkin wrote: > > I'd like to help on the graphics side, the current site kind of looks like > the python threw up all over the place. > > --- On Tue, 4/21/09, jug wrote: > > > From: jug > > Subject: [pygame] PyG

Re: [pygame] PyGame Website Rewrite

I'd like to help on the graphics side, the current site kind of looks like the python threw up all over the place. --- On Tue, 4/21/09, jug wrote: > From: jug > Subject: [pygame] PyGame Website Rewrite > To: pygame-users@seul.org > Date: Tuesday, April 21, 2009, 3:38 PM > Hello, > > Even if

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Okay, thanks! It went past that, but now its getting an error that says: /bin/sh: line 17: ./configure: No such file or directory Any idea whats going on here? On Wed, Apr 22, 2009 at 11:18 AM, Lenard Lindstrom wrote: > Hi Tyler, > > I wrote msys_build_deps.py and look after the Windows depende

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Hi Tyler, I wrote msys_build_deps.py and look after the Windows dependencies. I haven't seen this error before. I run the program on both Win 98 and XP. If you are using Msys 1.0.10 try upgrading to 1.0.11. I only user 1.0.10 because 1.0.11 doesn't work on Win 98 and I have limited access to X

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Not python under cygwin. Thats a leftover string from msys using cygwin code. The command I was trying to execute was python msys_build_deps.py --all Python is installed. Msys is installed, but throwing that error. And no worries. I just wasn't clear enough. :) -Tyler On Wed, Apr 22, 2009 at 10

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Tyler Laing wrote: The error says that it "Couldn't reserve space for cygwin's heap, Win32 error 6" when sh.exe was executed. Why are you trying to install Python under CygWin? From what I understand, most programmers consider that a separate platform from Windows. You should probably try t

Re: [pygame] C/C++ and Python

René Dudfield wrote: On Wed, Apr 22, 2009 at 7:39 PM, Knapp > wrote: Having worked in both languages, I have to say that with Python your head always feels clearer because you don't have 15 things that you are keeping track of in the back of your mind,

Re: beginning GSOC preparations: was Re: [pygame] Thank You

Rene, Okay, I am able to compile pygame on my linux desktop, and I've run into some issues with compiling for the windows guest vm I have. I already had my own blog, which I've made a relevant post on(as you can see from the posts to here and to soc2009-general). I've also added my blog to the rel

[pygame] New Blog

Hello all, I have a personal blog, of which I will be using during the GSoC project to make posts about my progress. The link is here: http://www.oddco.ca/zeroth/zblog/ Thank you, Tyler -- Visit my blog at http://oddco.ca/zeroth/zblog

Re: [pygame] Python 3.0 and Pygame Reloaded questions

Daniel McNeese : Thanks for the answers, Marcus. Some follow-up questions: Yes. Currently it's fixed to 32 joysticks to keep the memory manangement simple. It can be changed at any time to support (nearly) any amount of joysticks, if necessary, and will then just be limited by the SDL. 32

Re: [pygame] Python 3.0 and Pygame Reloaded questions

Thanks for the answers, Marcus. Some follow-up questions: > Yes. Currently it's fixed to 32 joysticks to keep the > memory manangement > simple. It can be changed at any time to support (nearly) > any amount of joysticks, if necessary, and will then just be > limited by the SDL. 32 is way more

Re: [pygame] msvcrt redistribution for Python 3.x (was: Python 3.0 and Pygame Reloaded questions)

Hi, here issome explanatory note regarding the msvcrt90.dll redistribution from the Python Win32 binary package: http://svn.python.org/view/python/trunk/Tools/msi/crtlicense.txt?revision=67859&view=markup Regards Marcus

Re: [pygame] Python 3.0 and Pygame Reloaded questions

Daniel McNeese : I'm working on a project in Game Maker, but it fails to meet my needs in one critical way: Game Maker only supports 2 joysticks/gamepads. I need more than that. So I'm taking a second look at Python, this time at 3.0 and the new version of Pygame. I have some que

Re: [pygame] C/C++ and Python

On Wed, Apr 22, 2009 at 7:39 PM, Knapp wrote: > > Having worked in both languages, I have to say that with Python your > head always feels clearer because you don't have 15 things that you > are keeping track of in the back of your mind, like the heap, points > to pointers, and more pointers etc.

Re: [pygame] Python 3.0 and Pygame Reloaded questions

Hi, python 3 is not very good for games. 1. it uses a newer version of the C dll than even msvcrt71.dll. 2. many 3rd party modules are not available for it. 3. it has removed support for many older platforms (win98, win2k < sp4, etc). 4. it is slower than python2.5 5. it is quite buggy in areas.

[pygame] Python 3.0 and Pygame Reloaded questions

I'm working on a project in Game Maker, but it fails to meet my needs in one critical way: Game Maker only supports 2 joysticks/gamepads. I need more than that. So I'm taking a second look at Python, this time at 3.0 and the new version of Pygame. I have some questions: 1) When last I looke

Re: [pygame] C/C++ and Python

On Wed, Apr 22, 2009 at 8:23 AM, René Dudfield wrote: > Indeed. > > However... one thing that people have told me why C is easier is this: > 'With python you need to come up with smarty pants algorithms, whereas in C > a simple brute force approach will work fast enough'. > > Which is also good, i