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 belopolsky
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:15:49
SpamBayes Score 7.137018e-06
Marked as misclassified No
Message-id <>
In-reply-to <>
2010/10/25 Jesús Cea Avión <>:
> 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?.

I would say compatibility with Sun/Apple probes should not stand in
the way of implementing this in cpython.  Of course familiarity to
existing users is a consideration, but in cases where self-consistency
can be improved, I don't think we should be overly concerned about
legacy scripts.  I would estimate that 90% of future users will never
have used either Sun or Apple probes, 9% will have used Apple and 1%
Sun. (This is completely unscientific guess, of course.)
Date User Action Args
2010-10-25 16:15:53belopolskysetrecipients: + belopolsky, rhettinger, jcea, ronaldoussoren, pitrou, wsanchez, movement, techtonik, giampaolo.rodola, glyph, bretthoerner, laca, twleung, jbaker, robert.kern, sirg3, chrismiles, danchr, dmalcolm, mjw, Garen, BreamoreBoy
2010-10-25 16:15:50belopolskylinkissue4111 messages
2010-10-25 16:15:49belopolskycreate