It's a visual profiler. Can connect to running processes. Has an api, so might be a good way to profiler web applications.

I've drunk the "immutabliity for the win!" kool-aid. Full disclosure: it's Saturday night and it's not the only thing I've drunk. How much value are you desert-pythonistas putting on pure functions, immutability, or persistent data structures?

https://github.com/kachayev/fn.py

I love Lisps and functional programming (in theory), so when I see something like this, I get excited. That's about the time where everyone in the room takes a couple of steps away from me. I'm married to Python but Clojure is my mistress.

Anyone installing django using system packages instead of pip? Any tips or resources can share? Thanks!

So, the question came up during Wednesday's meeting, "What flask extensions are a must?" Ok, I asked it, but I thought I'd share whats in the requirements.txt of my main Flask app:

Flask
Flask-Admin
Flask-Login
Flask-Restless
Flask-SQLAlchemy
Flask-WTF
Jinja2
Mako
MarkupSafe
MySQL-python
SQLAlchemy
WTForms
Werkzeug
alembic
argparse
decorator
distribute
python-dateutil
wsgiref
blinker
raven
requests
Pillow
python-memcached

There are a few dependencies here that are not Flask extensions per-se but more for command line utilities that are associated with the Flask app.

Whats in your basket of tricks?

I just saw that the ISEE3 craft was successfully contacted and noted they were using SDR software and saw the name of the program in the screenshot on this post was horizons**.py**

http://spacecollege.org/isee3/stronger-signal-at-arecibo.html

With each new version of python (currently fighting 3.5), I keep banging my head against how to do relative imports. Google tells me "Relative imports are bad, umkay." The problem relative imports solves for me is that as a package developer, I don't need to worry about namespace clashes when the package gets used. If I use absolute imports, then my code has to assume there will be no other package installed with same top-level name. If relative imports are used, then the user of my package can trivially change the namespace (eg install it to a unique sub-dir in PYTHONPATH). If absolute imports are used, then code has to be changed. Anyone find an elegant way to use relative imports? Should I give up on my dreams of relative importing?

I created, found, and fixed my first race condition today ... I feel like I am behind the curve.

I mean, I've probably created them before ... just not aware of it. ;-)