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 belopolsky, bretthoerner, chrismiles, danchr, dmalcolm, glyph, jbaker, jcea, laca, mjw, movement, rhettinger, robert.kern, ronaldoussoren, sirg3, skip.montanaro, twleung, wsanchez
Date 2010-02-26.19:00:25
SpamBayes Score 1.6359001e-05
Marked as misclassified No
Message-id <>
I have no experience integrating DTrace probes, so I guess would be a bit risky to trying to deal with this myself, since 2.7 deadline is pretty close.

If the only remaining issue is deciding about supporting SUN or Apple "style", and we have the risk of delaying this so much that we lose the 2.7 train, would be better to decide in one direction (I don't know about the difference, so I can't talk) and ship "something".

That is, if there is no reason to decide for A or B, we should use a coin to decide, instead of losing the opportunity of 2.7. DTrace is an amazing technology!

What do you think?
Date User Action Args
2010-02-26 19:00:27jceasetrecipients: + jcea, skip.montanaro, rhettinger, ronaldoussoren, belopolsky, wsanchez, movement, glyph, bretthoerner, laca, twleung, jbaker, robert.kern, sirg3, chrismiles, danchr, dmalcolm, mjw
2010-02-26 19:00:27jceasetmessageid: <>
2010-02-26 19:00:26jcealinkissue4111 messages
2010-02-26 19:00:26jceacreate