Yeah I apologize, "weird" isn't a useful description. I gave up on it and returned to 32-bit. To run all the tests, do I just invoke "nosetests" from inside the pyglet directory?
On Oct 30, 1:42 pm, Bruce Smith <[email protected]> wrote: > On Sun, Oct 30, 2011 at 8:25 AM, greenmoss <[email protected]> wrote: > > Is there any chance the ctypes-only clone will be integrated before a > > pyglet 1.2 release, or for that matter "any time soon"? FWIW, I tried > > the clone, and it was acting a bit "weird" for me. > > My $0.000002 on that would be that if tests show it clearly works better on > at least one configuration we want to support, we should seriously consider > integrating it. I have not looked inside it, but it seems like we could add > an option to use it, and the messiness would show up either as a lot of > tests for that option, or a lot of duplicated code (if the modules that > otherwise would have all those tests would have two variants instead). > Further, we might not be able to have a perfect automated choice for how to > set the option. But either of those situations seems better to me than just > not working well on some important system configuration. > > But until more test results are in, it's hard to discuss this concretely. > > Also it might be helpful if you would elaborate a bit on "acting a bit > weird" :-) > > - Bruce Smith -- 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.
