oh right. Thanks for testing. I guess that is a separate bug. Or maybe it can just be labeled under an 'oddity' or 'feature' ;)
But for the purposes of that bug, the Channel.play is working fine, so I'll close that bug. On Tue, Sep 6, 2011 at 6:43 PM, Christoph Gohlke <[email protected]> wrote: > > > On 9/6/2011 6:56 AM, René Dudfield wrote: > >> Hello, >> >> we have a bug report of a failure on python 3.1 with the >> pygame.mixer.Channel object. >> >> https://bitbucket.org/pygame/**pygame/issue/38/pygame-191-**mixer-bug<https://bitbucket.org/pygame/pygame/issue/38/pygame-191-mixer-bug> >> >> Can someone with python 3.1 or python3.2 confirm that this works or >> fails for them? You should hear a sound, and the the program finishes >> cleanly after 3 seconds. >> >> >> import pygame, pygame.examples, time, os >> pygame.init() >> main_dir = os.path.split(os.path.abspath(**pygame.examples.__file__))[0] >> data_dir = os.path.join(main_dir,'data') >> a_sound = pygame.mixer.Sound(os.path.**join(data_dir,"whiff.wav")) >> c = pygame.mixer.Channel(1); >> c.play(a_sound) >> time.sleep(3) >> >> > > For me this script does not work with any Python version on Windows unless > pygame.init() is replaced with pygame.mixer.init(). > > See also the first comment at > <http://pygame.org/docs/ref/**mixer.html<http://pygame.org/docs/ref/mixer.html> > > > > Christoph >
