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 ned.deily
Recipients Aaron.Meurer, BreamoreBoy, amaury.forgeotdarc, anacrolix, asvetlov, brechtm, eric.snow, ezio.melotti, giampaolo.rodola, jcea, josh.r, kachayev, kmike, meador.inge, ned.deily, pitrou, poke, python-dev, rhettinger, scoder, serhiy.storchaka
Date 2015-07-25.02:07:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437790042.03.0.634700023857.issue14373@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry about the delay in testing the patch.  I just confirmed (1) that I am still able to produce a segfault on OS X as described above under the specific conditions with a 10.6-like installer built with the current 3.5 tip and (2) that, with clru_cache_new.patch applied to the same current 3.5 tip, I no longer see the segfault.  So it looks like a fix.
History
Date User Action Args
2015-07-25 02:07:22ned.deilysetrecipients: + ned.deily, rhettinger, jcea, amaury.forgeotdarc, pitrou, scoder, giampaolo.rodola, ezio.melotti, asvetlov, poke, meador.inge, anacrolix, Aaron.Meurer, BreamoreBoy, python-dev, eric.snow, serhiy.storchaka, brechtm, kmike, kachayev, josh.r
2015-07-25 02:07:22ned.deilysetmessageid: <1437790042.03.0.634700023857.issue14373@psf.upfronthosting.co.za>
2015-07-25 02:07:22ned.deilylinkissue14373 messages
2015-07-25 02:07:21ned.deilycreate