Message151678
| Author |
techtonik |
| Recipients |
Garen, belopolsky, benjamin.peterson, danchr, dhduvall, dmalcolm, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, scox, serverhorror, sirg3, techtonik, twleung, wsanchez |
| Date |
2012年01月20日.08:18:50 |
| SpamBayes Score |
1.7964341e-08 |
| Marked as misclassified |
No |
| Message-id |
<CAPkN8xLQrk5T4KKnObLq-TGt1j-tHoCJN8F4KsfeKYUPLS4F1w@mail.gmail.com> |
| In-reply-to |
<1327035145.4992.109.camel@surprise> |
| Content |
I am an almost complete 0 in C system programming and in DTrace matters,
but I feel like DTrace has a potential to help me understand internal
CPython processes better. If maintenance of the code with DTrace is hard,
there are several ways to make it easier:
1. PyCon talk and a reference to video (why DTrace is cool for Python and
how to use it)
2. Chapter in Development guide explaining DTrace magic, how it works
3. Annotated example (like in "dive into" series) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年01月20日 08:18:51 | techtonik | set | recipients:
+ techtonik, loewis, rhettinger, jcea, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, benjamin.peterson, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, fche, hazmat, jmcp, scox |
| 2012年01月20日 08:18:50 | techtonik | link | issue13405 messages |
| 2012年01月20日 08:18:50 | techtonik | create |
|