I found a simple work-around for this. Empty the org.python.python.savedState folder, get info on it, then turn on the lock flag. The Python app will no longer be able to save state.
- Stoney On Nov 2, 2012, at 5:52 PM, Stonewall Ballard <[email protected]> wrote: > I found that I had to delete org.python.python.savedState each time before > running the tests in order to get the windows to show up. This explains why > it ran correctly only the first time I installed pyglet. > > If I delete the saved state, then run the "window" test by itself, it works > and does not generate new saved state. "window" will run repeatedly. If I run > the "app" test by itself first, it generates the saved state, and prevents > the "window" test from running subsequently, until the saved state is deleted. > > In particular, it's the file "data.data" within the saved state that's > causing the problem. If I remove only that file, the window test works. > > The tests "app", "font", "text", and "image" all generate the "data.data" > file. The others do not. > > I don't know why this is happening, but I hope that this info will clarify > things. > > I'm running 10.8.2 with the stock python on a Macbook Pro Retina. > > - Stoney -- Stonewall Ballard [email protected] http://stoney.sb.org/ -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
