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 zach.ware
Recipients Todd.Rovito, amaury.forgeotdarc, ezio.melotti, jkloth, loewis, pitrou, python-dev, roger.serwy, terry.reedy, trent, zach.ware
Date 2013-06-25.21:07:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKJDb-OzYB+TETbrr-g93qTu5swBBGNKSSUWcVwOB=jy37fHeg@mail.gmail.com>
In-reply-to <1372185398.94.0.159181208086.issue17883@psf.upfronthosting.co.za>
Content
> Jeremy Kloth added the comment:
>
> Although the solution for test_ttk_guionly of disabling the gui resource is a good quick fix, I'm curious as to why there isn't the same issue (test hangs) when run using 3.3 on the same machine.

As it turns out, 3.3(+)'s test.support has an _is_gui_available
function that prevents the hang, added in issue9931.  Ironically, it
was not added to 2.7 because the 2.7 buildbots weren't showing
symptoms...because the tests weren't actually being run.

I'll work on trying to backport the patch that added
_is_gui_available, but my experience with ctypes is practically nil,
so if anyone can get to it before I can post a patch, don't hold off
on my account.
History
Date User Action Args
2013-06-25 21:07:19zach.waresetrecipients: + zach.ware, loewis, terry.reedy, amaury.forgeotdarc, pitrou, jkloth, trent, ezio.melotti, roger.serwy, Todd.Rovito, python-dev
2013-06-25 21:07:19zach.warelinkissue17883 messages
2013-06-25 21:07:19zach.warecreate