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 jcea
Recipients BreamoreBoy, Garen, belopolsky, bretthoerner, chrismiles, danchr, dmalcolm, giampaolo.rodola, glyph, jbaker, jcea, laca, mjw, movement, pitrou, rhettinger, robert.kern, ronaldoussoren, sirg3, techtonik, twleung, wsanchez
Date 2010-10-25.16:03:02
SpamBayes Score 3.271945e-05
Marked as misclassified No
Message-id <1288022586.34.0.216868175839.issue4111@psf.upfronthosting.co.za>
In-reply-to
Content
I am trying to review this for 3.2, but I am having some issues. For instance, "include/pydtrace.d" is not present in the last patch.

Please, post a patch with all the required changes in the same (patch) file. Hurry, we are still on track for 3.2. :-).

Another question: I am not able to decide between Sun/Apple style, or breaking dtrace scripts compatibility completely. Anybody has an opinion about this?. Is this actually important?. Are there so many legacy dtrace scripts out there?.
History
Date User Action Args
2010-10-25 16:03:06jceasetrecipients: + jcea, rhettinger, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, techtonik, giampaolo.rodola, glyph, bretthoerner, laca, twleung, jbaker, robert.kern, sirg3, chrismiles, danchr, dmalcolm, mjw, Garen, BreamoreBoy
2010-10-25 16:03:06jceasetmessageid: <1288022586.34.0.216868175839.issue4111@psf.upfronthosting.co.za>
2010-10-25 16:03:03jcealinkissue4111 messages
2010-10-25 16:03:02jceacreate