This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Robin.Schreiber
Recipients Robin.Schreiber
Date 2012-08-18.10:53:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345287224.98.0.204885883161.issue15721@psf.upfronthosting.co.za>
In-reply-to
Content
Changes proposed in PEP3121 and PEP384 have now been applied to the tkinter module!
When running the test form inside Python.exe (tkinter._test()), the litte "test-window" is rendered correctly. However there are still some error messages popping up inside the python shell 
(I am running this on OS X 10.8):

>>> tkinter._test()
2012-08-18 12:46:24.775 python.exe[17410:707] speedup (null)
2012-08-18 12:46:24.776 python.exe[17410:707] ERROR: Unable to find method [_NSFullScreenTransition _startFullScreenTransitionForCGWindow:targetFrame:duration:].
2012-08-18 12:46:24.776 python.exe[17410:707] ERROR: Unable to find method [_NSFullScreenTransition _startEnterFullScreenTransitionForCGWindow:targetFrame:duration:].
2012-08-18 12:46:24.778 python.exe[17410:707] ERROR: Unable to find method [_NSFullScreenTransition startExitFullScreenTransitionForCGWindow:targetFrame:duration:].
[87221 refs]
>>> 

I have no Idea how and where these are triggered.
History
Date User Action Args
2012-08-18 10:53:45Robin.Schreibersetrecipients: + Robin.Schreiber
2012-08-18 10:53:44Robin.Schreibersetmessageid: <1345287224.98.0.204885883161.issue15721@psf.upfronthosting.co.za>
2012-08-18 10:53:43Robin.Schreiberlinkissue15721 messages
2012-08-18 10:53:43Robin.Schreibercreate