HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wyplay
pytracemalloc
Python2013–2014
wyplay / pytracemalloc

pytracemalloc

This project is no longer maintained here, instead, for Python < 3.4, please see 'https://github.com/haypo/pytracemalloc', maintained by Victor Stinner.

2Distinct people
2Mentions
0Explicit recommenders
91GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This project is no longer maintained here, instead, for Python < 3.4, please see 'https://github.com/haypo/pytracemalloc', maintained by Victor Stinner.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2013-11-25 17:33:34 UTC to 2014-03-21 18:13:46 UTC. Weeks start Monday, UTC.

012013-11-25 00:00:00 UTC to 2013-12-02 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 252013-12-02 00:00:00 UTC to 2013-12-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-09 00:00:00 UTC to 2013-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 00:00:00 UTC to 2013-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-23 00:00:00 UTC to 2013-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-30 00:00:00 UTC to 2014-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-06 00:00:00 UTC to 2014-01-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-13 00:00:00 UTC to 2014-01-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-20 00:00:00 UTC to 2014-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 202014-01-27 00:00:00 UTC to 2014-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-03 00:00:00 UTC to 2014-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-10 00:00:00 UTC to 2014-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-17 00:00:00 UTC to 2014-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-24 00:00:00 UTC to 2014-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-03 00:00:00 UTC to 2014-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-10 00:00:00 UTC to 2014-03-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-17 00:00:00 UTC to 2014-03-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 17

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 252013-11-25 00:00:00 UTC2013-12-02 00:00:00 UTC101
Dec 22013-12-02 00:00:00 UTC2013-12-09 00:00:00 UTC000
Dec 92013-12-09 00:00:00 UTC2013-12-16 00:00:00 UTC000
Dec 162013-12-16 00:00:00 UTC2013-12-23 00:00:00 UTC000
Dec 232013-12-23 00:00:00 UTC2013-12-30 00:00:00 UTC000
Dec 302013-12-30 00:00:00 UTC2014-01-06 00:00:00 UTC000
Jan 62014-01-06 00:00:00 UTC2014-01-13 00:00:00 UTC000
Jan 132014-01-13 00:00:00 UTC2014-01-20 00:00:00 UTC000
Jan 202014-01-20 00:00:00 UTC2014-01-27 00:00:00 UTC000
Jan 272014-01-27 00:00:00 UTC2014-02-03 00:00:00 UTC000
Feb 32014-02-03 00:00:00 UTC2014-02-10 00:00:00 UTC000
Feb 102014-02-10 00:00:00 UTC2014-02-17 00:00:00 UTC000
Feb 172014-02-17 00:00:00 UTC2014-02-24 00:00:00 UTC000
Feb 242014-02-24 00:00:00 UTC2014-03-03 00:00:00 UTC000
Mar 32014-03-03 00:00:00 UTC2014-03-10 00:00:00 UTC000
Mar 102014-03-10 00:00:00 UTC2014-03-17 00:00:00 UTC000
Mar 172014-03-17 00:00:00 UTC2014-03-24 00:00:00 UTC101

What Hacker News says

2 sources
GNU/Linux emacs user for Python dev. The ability to browser a code easily, when you don't actually know the code, is a lot of time that will be saved. Pycharm is the best tool I know that does it out of the box. I don't know about its debugging facility (I think you mean setting break points), probably https://github.com/narfdotpl/debug will work just fine. I've been doing 1 year and a half of debugging Python code and used it three times. Most of the time the workflow is this: 0) add logs? 1) reproduce the bug 2) read the logs? 3) read the code? 4) if the best fix is found fix it else restart at 0) Other useful tools for debugging: - http://dpaste.com/hold/1751069/ this is the basic version of what I use at work. It's a data descriptor [1] - http://faulthandler.readthedocs.org/ "for when there is no traceback" - Since you do UI, most lik
Read the rest
ely you'll deal with asynchronous callback style code (non-yield based), the traceback of a callback is not always useful ie. you want to know to which code it is answering to. For that matter you need tweak the event-loop code... having this patch at hand is helpful. e.g. say you do a asynchronous call to retrieve something in the database, the call probably looks like "query(callback=query_callback)", when the "query_callback" will be called by the event loop with the result of the query as arguments, most likely the immediate top frame is the event-loop (if it's not the previous frame, it's the one before...) and "query" function will not be in the callstack of course... If "query_callback" is used as a callback of several asynchronous calls, you can not find the "calling code" with "find usage" of your IDE... I think asyncio fix this Profiling: - http://www.vrplumber.com/programming/runsnakerun/ - https://github.com/bdarnell/plop - https://github.com/wyplay/pytracemalloc it is integrated in Python 3.4 I also use gdb on python coredumps. [1] http://www.cafepy.com/article/python_attributes_and_methods/...
In Ask HN: Getting back into Python

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.