[pygame] status report

2009-07-09 Thread jug

Hello,

Time marches on, so some words about the current state of affairs.
First, I've to say that Orcun unfortunately is not any longer in our team.
Then, a slightly more delightful point, we are near at the finish! Only some
minor points and improvements are left, then we can start a final testing
period.

Points left to do:

   Devon:
 * Complete the modern design before starting with a new one
* finish form design
* design administrative links like buttons (edit project, 
release.., ...)

* ticket #5
* ...
 * update the trac theme to fit the current design
(maybe ask coderanger at #pygame to help you, he did the 
current desgin plugin)


   Marcus:
 * get the current db and help to write convert scripts
 * convince the rest of the pygame core team
 * review templates
 * test the website, its features, admin functionality, etc.
 * help me with ordering/collecting ToDos and design decisions

   Julian:
 * well, I've to do everything else :-)

I'll collect the hangover from my various ToDo lists and bring it to the 
wiki page.


I also made a features list: http://pygameweb.no-ip.org/trac/wiki/Features
In case I've forgotten anything please add it to this list.

I hope to complete this project soon and see it running on pygame.org

Regards,
Julian


[pygame] [BUG] midi unit test for Pygame rev 2500, Python 2.6.2, Windows XP

2009-07-09 Thread Lenard Lindstrom

Hi,

The Python 1.9.0 rc 3 unit tests fail with the following midi related bug:

==
ERROR: MidiTest.test_get_device_info
--
Traceback (most recent call last):
 File C:\python26\lib\site-packages\pygame\tests\midi_test.py, line 
400, in t

est_get_device_info
   raise Exception(repr(r))
Exception: None

--

Lenard




[pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread Lenard Lindstrom

Hi everyone,

Here is the latest Pygame 1.9.0 (rev 2500) for Python 2.6 on Windows. 
Though the machine this was compiled on has a firewall and active 
antivirus program, it uses XP and is not mine, so take whatever 
precautions you feel necessary. The msi installer is:


http://www3.telus.net/len_l/pygame/pygame-1.9.0b03win32-py2.6.msi

md5sum:
e247f69466be1f847c875794cc01d173

There is no corresponding Python 3.1 version. A distutils bug, absent in 
Python 3.0 and fixed in Python 2.6.2, prevents compilation with MinGW.


Enjoy,

Lenard Lindstrom



Re: [pygame] Incrementing the frequency of the Pygame.mixer with a Loop?

2009-07-09 Thread Brian Gryder
Thanks for the reply Lenard,  I tried your suggestion and the pitch is still
not changing as the frequency increments with the loop.

This is a strange issue. if I manually change the value if frequency before
I run it, the sound changes. it is as if the pygame.mixer's parameters are
Stuckand can't be changed during runtime. Is there a way I can verify that
the pygame.mixer and the sound objects are unloaded before I restart the
loop?

Is there anything else I can try? Any links or snippet of code would be
greatly appreciated.

Here is the updated program
-
import pygame
from pygame.locals import *
from sys import exit

#pgyame.display.set_mode must also come after the pygame.init. The display
is not necessary for mixer though. -Lenard
#screen = pygame.display.set_mode((800, 600), 0, 32)
frequency = 44100
while True:
frequency = frequency + 2000
print frequency
pygame.mixer.pre_init(frequency, 16, 2, 4096)
pygame.init()
test_sound = pygame.mixer.Sound(check.wav)
mychannel = test_sound.play()
while pygame.mixer.get_busy() == True:
pass
pygame.quit # do a pygame.quit rather than pygame.mixer.quit for each
loop -Lenard


---


On Wed, Jul 8, 2009 at 2:26 AM, Lenard Lindstrom le...@telus.net wrote:

 Hi Brian,

 You would probably have to do a pygame.quit rather than pygame.mixer.quit
 for each pass of the loop. The pgyame.display.set_mode must also come after
 the pygame.init. The display is not necessary for mixer though.

 Lenard


 Brian Gryder wrote:

 '''
 How do I change the frequency of the Pygame.mixer by incrementing the
 frequency value in a loop?

 Please see the example below where I am trying to initialize the frequency
 at 44100 and then add 2000 to the frequency each time it loops. In this
 example below the pitch does not change, I really want it to change.

 Any links or snippet of code would be greatly appreciated, Thanks!
  '''

 import pygame
 from pygame.locals import *
 from sys import exit

 screen = pygame.display.set_mode((800, 600), 0, 32)
 frequency = 44100

 while True:

frequency = frequency + 2000
print frequency

pygame.mixer.pre_init(frequency, 16, 2, 4096)
pygame.init()
test_sound = 
test_sound = pygame.mixer.Sound(check.wav)
mychannel = test_sound.play()

while pygame.mixer.get_busy() == True:
pass
#passing

pygame.mixer.quit






Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread René Dudfield
Hello,

awesome.  I'll put it up with the other rc3 stuff.

typo with the link:
http://www3.telus.net/len_l/pygame/pygame-1.9.0b03.win32-py2.6.msi

cheers!


On Fri, Jul 10, 2009 at 8:15 AM, Lenard Lindstrom le...@telus.net wrote:

 Hi everyone,

 Here is the latest Pygame 1.9.0 (rev 2500) for Python 2.6 on Windows.
 Though the machine this was compiled on has a firewall and active antivirus
 program, it uses XP and is not mine, so take whatever precautions you feel
 necessary. The msi installer is:

 http://www3.telus.net/len_l/pygame/pygame-1.9.0b03win32-py2.6.msi

 md5sum:
 e247f69466be1f847c875794cc01d173

 There is no corresponding Python 3.1 version. A distutils bug, absent in
 Python 3.0 and fixed in Python 2.6.2, prevents compilation with MinGW.

 Enjoy,

 Lenard Lindstrom




Re: [pygame] Incrementing the frequency of the Pygame.mixer with a Loop?

2009-07-09 Thread Lenard Lindstrom

Hi,

You have pygame.quit instead of pygame.quit() .

Lenard

Brian Gryder wrote:
Thanks for the reply Lenard,  I tried your suggestion and the pitch is 
still not changing as the frequency increments with the loop.


This is a strange issue. if I manually change the value if frequency 
before I run it, the sound changes. it is as if the pygame.mixer's 
parameters are Stuckand can't be changed during runtime. Is there a 
way I can verify that the pygame.mixer and the sound objects are 
unloaded before I restart the loop?


Is there anything else I can try? Any links or snippet of code would 
be greatly appreciated.


Here is the updated program
-
import pygame
from pygame.locals import *
from sys import exit

#pgyame.display.set_mode must also come after the pygame.init. The 
display is not necessary for mixer though. -Lenard

#screen = pygame.display.set_mode((800, 600), 0, 32)
frequency = 44100
while True:
frequency = frequency + 2000
print frequency
pygame.mixer.pre_init(frequency, 16, 2, 4096)
pygame.init()
test_sound = pygame.mixer.Sound(check.wav)
mychannel = test_sound.play()
while pygame.mixer.get_busy() == True:
pass
pygame.quit # do a pygame.quit rather than pygame.mixer.quit for 
each loop -Lenard



---



On Wed, Jul 8, 2009 at 2:26 AM, Lenard Lindstrom le...@telus.net 
mailto:le...@telus.net wrote:


Hi Brian,

You would probably have to do a pygame.quit rather than
pygame.mixer.quit for each pass of the loop. The
pgyame.display.set_mode must also come after the pygame.init. The
display is not necessary for mixer though.

Lenard


Brian Gryder wrote:

'''
How do I change the frequency of the Pygame.mixer by
incrementing the frequency value in a loop?

Please see the example below where I am trying to initialize
the frequency at 44100 and then add 2000 to the frequency each
time it loops. In this example below the pitch does not
change, I really want it to change.

Any links or snippet of code would be greatly appreciated, Thanks!
 '''

import pygame
from pygame.locals import *
from sys import exit

screen = pygame.display.set_mode((800, 600), 0, 32)
frequency = 44100

while True:

   frequency = frequency + 2000
   print frequency

   pygame.mixer.pre_init(frequency, 16, 2, 4096)
   pygame.init()
   test_sound = 
   test_sound = pygame.mixer.Sound(check.wav)
   mychannel = test_sound.play()

   while pygame.mixer.get_busy() == True:
   pass
   #passing

   pygame.mixer.quit








[pygame] ANNOUNCE: pygame1.9.0rc3 - almost last release candidate!

2009-07-09 Thread René Dudfield
*___**  _  _ __ ___  _   _
|| \ \\ // \  //\ ||\/|  /|\
|| |  \\   /||   //  \|| \  / |  ||
|--/   \\_/ ||==//\   ||  \/  |  |||
**|**|  ||  ||||   //  \  ||  |  ||
**|**|  ||   \/   //\ ||  |  \=/
   *.
   *o*
  *1.9.0RC3* *r*
   *g*
O
  \/__
 * /*
*()()  *More RC for you ♥*
* \ \
  \_\_

(last chance to get any last minute bug fixes in...).


What's new (heaps of things since 1.8.1):
  http://www.pygame.org/whatsnew.shtml

Summary of changes:
- many, many fixes and improvements.  The largest amount of changes has gone
into this release than any other pygame release.
- bug fixes for backwards compatibility issues introduced in pygame 1.8.x
series.  old games like solarwolf and libraries like PGU work again.
- experimental *camera* webcam module (still in development).
- experimental midi module based on portmidi and pyportmidi (99% complete).
- experimental gfxdraw module based on SDL_gfx (including AA circles, textured
polygons and other goodness).
- python3, and python3.1 support mostly completed.  Some modules still
remain to be completed - but mostly it's working.
- nokia mobile phone s60 support.
- improved OSX support (dropped pyobjc dependency, improved installer,
sysfont now works on OSX).
- pygame.examples + pygame.tests included with pygame.  This makes testing
easier, and also makes learning pygame more fun and easy.
- cleanup of examples, and addition of new examples.
- new tools to aid in development of pygame itself, better compilation
documentation.
- py2app, and py2exe support improved.



This should be the last RC release candidate before the real 1.9.0 is
released... so if you find any bugs please let us know.


Source code release (binaries at bottom of announcement):
  http://pygame.googlecode.com/files/pygame-1.9.0rc3.tar.gz(2.2MB)
  http://pygame.googlecode.com/files/pygame-1.9.0rc3.zip(2.0MB)

  Compilation instructions for different platforms:
  http://www.pygame.org/wiki/Compilation



After install, it'd be nice if you could do a self test with:
python -m pygame.tests

Testing that your games still work with pygame 1.9.0rc3 would be a great
help.  Or test other peoples games if you want to help :)

Some binaries below...  for the build page...  anyone able to make other
binaries(nokia, windows python2.6/2.4 binaries needed)?

cheers!





See a list of examples...
  python -c import pygame.examples;help(pygame.examples)

Run one of the 30 examples included...
  python -m pygame.examples.aliens




RC3 binary builds for win/mac from the The Spectacularly Adequate Automated
Pygame Build Page.

OSX 10.4/10.5/10.6 universal(intel and ppc):
  http://pygame.googlecode.com/files/pygame-1.9.0rc3-py2.6-macosx10.5.zip10.3MB
  http://pygame.googlecode.com/files/pygame-1.9.0rc3-py2.5-macosx10.5.zip10.3MB
  http://pygame.googlecode.com/files/pygame-1.9.0rc3-py2.4-macosx10.5.zip10.3MB

Windows:
  http://pygame.googlecode.com/files/pygame-1.9.0b03.win32-py2.5.msi 3MB
  http://pygame.googlecode.com/files/pygame-1.9.0rc3.win32-py2.5.exe 3MB
  http://pygame.googlecode.com/files/pygame-1.9.0b03.win32-py2.6.msi 3MB
(thanks to Lenard for making this)

The build page is missing working python2.4(uses old prebuilts, tests
failing) and python2.6 builds for windows...  Lenard has provided a nice
python2.6 build for windows.

Also missing nokia pys60 builds, and python3.1 builds for windows and mac.
Binaries for linux distros (ubuntu etc are generated by them).


MD5 (pygame-1.9.0rc3.tar.gz) = a8e8a7c835176edcbf007af5232c67af
MD5 (pygame-1.9.0rc3.zip) = 5bc31354693786205e1493c50a3f189a

MD5 (pygame-1.9.0b03.win32-py2.5.msi) = c0ff7ca91d965eb630b12649591c43c3
MD5 (pygame-1.9.0rc3.win32-py2.5.exe) = e26ed7e8ce774883b673b7759590b9f4
MD5 (pygame-1.9.0b03.win32-py2.6.msi) = e247f69466be1f847c875794cc01d173

MD5 (pygame-1.9.0rc3-py2.4-macosx10.5.zip) =
b885acfd4e602826c9cadbe8d7272d7d
MD5 (pygame-1.9.0rc3-py2.5-macosx10.5.zip) =
3931517f7bd9dc4f424c632dc2226def
MD5 (pygame-1.9.0rc3-py2.6-macosx10.5.zip) =
982f966e601cf3a3acfda1d9f794a769


Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread claudio canepa
On Thu, Jul 9, 2009 at 8:55 PM, René Dudfield ren...@gmail.com wrote:

 Hello,

 awesome.  I'll put it up with the other rc3 stuff.

 typo with the link:
 http://www3.telus.net/len_l/pygame/pygame-1.9.0b03.win32-py2.6.msi

 cheers!


 On Fri, Jul 10, 2009 at 8:15 AM, Lenard Lindstrom le...@telus.net wrote:

 Hi everyone,

 Here is the latest Pygame 1.9.0 (rev 2500) for Python 2.6 on Windows.
 Though the machine this was compiled on has a firewall and active antivirus
 program, it uses XP and is not mine, so take whatever precautions you feel
 necessary. The msi installer is:

 http://www3.telus.net/len_l/pygame/pygame-1.9.0b03win32-py2.6.msi

 md5sum:
 e247f69466be1f847c875794cc01d173

 There is no corresponding Python 3.1 version. A distutils bug, absent in
 Python 3.0 and fixed in Python 2.6.2, prevents compilation with MinGW.

 Enjoy,

 Lenard Lindstrom


 Thanks for the build !!!
1. In the section 'Tests', the docs tells:

A quick way to run the test suite package from the command line is to
import the go submodule

with the Python -m option:

  python -m pygame.tests [test options]


but in winXP, python 2.6.1 this not works:


D:\tmpc:\python26\python.exe -m pygame.tests
c:\python26\python.exe: pygame.tests is a package and cannot be directly
executed


Making a script pygame19rc3_starter.py with the contents:

#test starter
from pygame.tests import run
run()
#script ends

and running with

D:\tmpc:\python26\python.exe -m pygame19rc3_starter.py

the tests runs.

--
2. The test run goes ok:
...
Ran 412 tests in 62.766s

OK

--
3. playtested some games and old bugdemos, no problems
--
thanks !
--
claxo


Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread René Dudfield
On Fri, Jul 10, 2009 at 12:06 PM, claudio canepa ccanep...@gmail.comwrote:



 On Thu, Jul 9, 2009 at 8:55 PM, René Dudfield ren...@gmail.com wrote:

 Hello,

 awesome.  I'll put it up with the other rc3 stuff.

 typo with the link:
 http://www3.telus.net/len_l/pygame/pygame-1.9.0b03.win32-py2.6.msi

 cheers!


 On Fri, Jul 10, 2009 at 8:15 AM, Lenard Lindstrom le...@telus.netwrote:

 Hi everyone,

 Here is the latest Pygame 1.9.0 (rev 2500) for Python 2.6 on Windows.
 Though the machine this was compiled on has a firewall and active antivirus
 program, it uses XP and is not mine, so take whatever precautions you feel
 necessary. The msi installer is:

 http://www3.telus.net/len_l/pygame/pygame-1.9.0b03win32-py2.6.msi

 md5sum:
 e247f69466be1f847c875794cc01d173

 There is no corresponding Python 3.1 version. A distutils bug, absent in
 Python 3.0 and fixed in Python 2.6.2, prevents compilation with MinGW.

 Enjoy,

 Lenard Lindstrom


 Thanks for the build !!!
 1. In the section 'Tests', the docs tells:

 A quick way to run the test suite package from the command line is to
 import the go submodule

 with the Python -m option:

   python -m pygame.tests [test options]
 

 but in winXP, python 2.6.1 this not works:


 D:\tmpc:\python26\python.exe -m pygame.tests
 c:\python26\python.exe: pygame.tests is a package and cannot be directly
 executed


 Making a script pygame19rc3_starter.py with the contents:

 #test starter
 from pygame.tests import run
 run()
 #script ends

 and running with

 D:\tmpc:\python26\python.exe -m pygame19rc3_starter.py

 the tests runs.

 --
 2. The test run goes ok:
 ...
 Ran 412 tests in 62.766s

 OK

 --
 3. playtested some games and old bugdemos, no problems
 --
 thanks !
 --
 claxo




Ah, damn.  I notice this on ubuntu, and OSX with python2.6 too...

However it works with python3.0 and python3.1

Here's the python bug:
http://bugs.python.org/issue2751

Looks like someone just decided to break it in python2.6.  I guess they
haven't ported the brokenness to py3k yet.

Maybe we should use:

python -m pygame.tests.main
python -m pygame.examples.main

A bit uglier, but it will at least work!


cheers,


Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread claudio canepa
On Thu, Jul 9, 2009 at 11:48 PM, René Dudfield ren...@gmail.com wrote:


 ...

 Maybe we should use:

 python -m pygame.tests.main
 python -m pygame.examples.main

 A bit uglier, but it will at least work!


 cheers,

just FYI:
D:\tmpc:\python26\python.exe -m pygame.tests.main
c:\python26\python.exe: No module named pygame.tests.main
--
claxo


Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread Lenard Lindstrom

René Dudfield wrote:



On Fri, Jul 10, 2009 at 12:06 PM, claudio canepa ccanep...@gmail.com 
mailto:ccanep...@gmail.com wrote:




On Thu, Jul 9, 2009 at 8:55 PM, René Dudfield ren...@gmail.com
mailto:ren...@gmail.com wrote:

Hello,

awesome.  I'll put it up with the other rc3 stuff.

typo with the link:
   
http://www3.telus.net/len_l/pygame/pygame-1.9.0b03.win32-py2.6.msi


cheers!



On Fri, Jul 10, 2009 at 8:15 AM, Lenard Lindstrom
le...@telus.net mailto:le...@telus.net wrote:

Hi everyone,

Here is the latest Pygame 1.9.0 (rev 2500) for Python 2.6
on Windows. Though the machine this was compiled on has a
firewall and active antivirus program, it uses XP and is
not mine, so take whatever precautions you feel necessary.
The msi installer is:

http://www3.telus.net/len_l/pygame/pygame-1.9.0b03win32-py2.6.msi

md5sum:
e247f69466be1f847c875794cc01d173

There is no corresponding Python 3.1 version. A distutils
bug, absent in Python 3.0 and fixed in Python 2.6.2,
prevents compilation with MinGW.

Enjoy,

Lenard Lindstrom


Thanks for the build !!!
1. In the section 'Tests', the docs tells:

A quick way to run the test suite package from the command line
is to import the go submodule 

with the Python -m option: 


  python -m pygame.tests [test options]


but in winXP, python 2.6.1 this not works:
 


D:\tmpc:\python26\python.exe -m pygame.tests
c:\python26\python.exe: pygame.tests is a package and cannot be
directly executed


Making a script pygame19rc3_starter.py with the contents:

#test starter
from pygame.tests import run
run()
#script ends

and running with

D:\tmpc:\python26\python.exe -m pygame19rc3_starter.py

the tests runs.

--
2. The test run goes ok: 
...

Ran 412 tests in 62.766s

OK

--
3. playtested some games and old bugdemos, no problems 
--

thanks !
--
claxo




Ah, damn.  I notice this on ubuntu, and OSX with python2.6 too...

However it works with python3.0 and python3.1

Here's the python bug:
http://bugs.python.org/issue2751

Looks like someone just decided to break it in python2.6.  I guess 
they haven't ported the brokenness to py3k yet.


Maybe we should use:

python -m pygame.tests.main
python -m pygame.examples.main

A bit uglier, but it will at least work!


cheers,

Hi,

python -m pygame.tests.__main__
python -m pygame.docs.__main__

There would be no reason to run pygame.examples, right?

The explanation I found was that being able to run a package in Python 
2.5 was considered a bug, so was fixed in Python 2.6. Adding __main__.py 
as an entry point for running a package in Python 2.7 and 3.0 is an 
attempt repair the fix.


Lenard



Re: [pygame] Pygame 1.9.0 release candidate 3 for Python 2.6 on Windows

2009-07-09 Thread René Dudfield
On Fri, Jul 10, 2009 at 2:25 PM, Lenard Lindstrom le...@telus.net wrote:

 Hi,

 python -m pygame.tests.__main__
 python -m pygame.docs.__main__

 There would be no reason to run pygame.examples, right?



Yeah, maybe __main__ is good.  Perhaps pygame.tests should have a __main__
function too?

 import pygame.tests
 pygame.tests.main()

Since main() is what is used in the examples, it would be nice to try and
keep it the same.  But then we need to add a main.py and a __main__.py...
ew.




You can do a self test with:
python -m pygame.tests
Or with python2.6 do:
python -m pygame.tests.__main__


Doing it for examples could list which examples are available?


$ python -m pygame.examples
aacircle
aliens
arraydemo
blend_fill
blit_blends
camera
chimp
cursors
eventlist
fastevents
fonty
glcube
headless_no_windows_needed
liquid
mask
midi
moveit
movieplayer
oldalien
overlay
pixelarray
scaletest
scrap_clipboard
scroll
sound
sound_array_demos
stars
testsprite
vgrade


eg.


See a list of examples...
  python -m pygame.examples
Or with python2.6,
  python -m pygame.examples.__main__

Run one of the 30 examples included...
  python -m pygame.examples.aliens


I'm not sure anyone would remember to add __main__ at the end(or even
main).  oh well.


There might be a workaround...  One work around might be to make it into a
module-module, not a package-module.  Then have the module-module load the
package-module into its namespace.





 The explanation I found was that being able to run a package in Python 2.5
 was considered a bug, so was fixed in Python 2.6. Adding __main__.py as an
 entry point for running a package in Python 2.7 and 3.0 is an attempt repair
 the fix.

 Lenard