Message 198254 - Python tracker

➜

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	ncoghlan
Recipients	bkabrda, dmalcolm, ncoghlan, pitrou, rhettinger, skrah, vstinner
Date	2013-09-22.09:43:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1379843026.19.0.17979478464.issue19001@psf.upfronthosting.co.za>
In-reply-to

Content
Looks like the RHEL 6 failures may have just been a change on the OS side that reintroduced the need for this old workaround: http://docs.python.org/devguide/faq.html#how-do-i-update-my-auto-load-safe-path-to-allow-test-gdb-to-run I restored that FAQ, applied the config change on the buildbot and fixed the 2.7 branch to skip rather than fail (as it was previously supposed to, but the line that actually did the skip was lost in a backport from 3.x somewhere along the line).

Looks like the RHEL 6 failures may have just been a change on the OS side that reintroduced the need for this old workaround: http://docs.python.org/devguide/faq.html#how-do-i-update-my-auto-load-safe-path-to-allow-test-gdb-to-run

I restored that FAQ, applied the config change on the buildbot and fixed the 2.7 branch to skip rather than fail (as it was previously supposed to, but the line that actually did the skip was lost in a backport from 3.x somewhere along the line).

History
Date	User	Action	Args
2013-09-22 09:43:46	ncoghlan	set	recipients: + ncoghlan, rhettinger, pitrou, vstinner, skrah, dmalcolm, bkabrda
2013-09-22 09:43:46	ncoghlan	set	messageid: <1379843026.19.0.17979478464.issue19001@psf.upfronthosting.co.za>
2013-09-22 09:43:46	ncoghlan	link	issue19001 messages
2013-09-22 09:43:45	ncoghlan	create