Terminal move cursor with mouse in any way? - Apple
yesterday
In Apple's Terminal.app, you can option-click to move the cursor with the mouse.
from twitter
yesterday
regex - Perl Compatible Regular Expression (PCRE) in Python - Stack Overflow
7 days ago
advanced (unicode) Regular Expressions in python
python
7 days ago
Just-in-case versus just-in-time — The Endeavour
a case for learning things we dont yet need to know
8 days ago
List Python Packages : Clark's Tech Blog
12 days ago
Just a short script related to that update all easy_install packages script I linked to the other day. I wanted a nice list of what the heck I’ve actually installed over the years. The following is a quick and dirty way to do this.
python
via:Boinside
12 days ago
Letters of Note: Love, Dad
13 days ago
charm with one woman for the rest of your life. Any man can find a twerp here and there who will go along with cheating, and it doesn't take all that much manhood. It does take quite a man to remain attractive and to be loved by a woman who has heard him snore, seen him un
via:noahread
13 days ago
How Common Is Your Birthday? | The Daily Viz
Very cool heat map showing birth patterns.
Check out the gaps around major holidays
16 days ago
Check out the gaps around major holidays
Strategic line breaks - Nathan’s Blog
17 days ago
Here is a script for BBEdit to insert a line break after the most recent comma or period.
from twitter
17 days ago
Git hg rosetta stone · sympy/sympy Wiki · GitHub
18 days ago
This is a useful reference for hg users forced to contend with git. Also, observe how terse the hg column is:
from twitter_favs
18 days ago
rwilcox/git.bbpackage - GitHub
20 days ago
A BBEdit package to make working with Git easier
git
BBEdit
via:neurobashing
20 days ago
bbedit at master from isao/shell - GitHub
20 days ago
various scripts and support files for noodling on the command line, especially programming with bbedit, git/gitx
BBEdit
via:neurobashing
20 days ago
Untitled (http://twitter.com/Alex_Ogle/status/199907798153302017/photo/1)
23 days ago
RT @Alex_Ogle: Pretty epic typo for Benedict Cumberbatch in Washington Post, third paragraph (via @sstummeafp)
from twitter
23 days ago
The problem with Sturges' rule for constructing histograms (sturges histogram - Google Search)
calculating bin width for histograms.
23 days ago
Learn something new every day: Debugging with Python (PDB) - Quick and Easy Tutorial
24 days ago
So here is my own personal gentle introduction to using pdb. It assumes that you are not using any IDE -- that you're coding Python with a text editor and running your Python programs from the command line.
python
24 days ago
Turn a BeautifulSoup form in to a dict of fields and default values - useful for screen scraping forms and then resubmitting them — Gist
25 days ago
Turn a BeautifulSoup form in to a dict of fields and default values - useful for screen scraping forms and then resubmitting them
python
25 days ago
Stop Using “print” for Debugging: A 5 Minute Quickstart Guide to Python’s logging Module
25 days ago
This tutorial is short.
To figure out bugs in your code, you might put in print statements/print() calls to display the value of variables.
Don’t do this. Use the Python logging module.
The logging is better than printing because:
It’s easy to put a timestamp in each message, which is very handy.
You can have different levels of urgency for messages, and filter how less urgent messages.
When you want to later find/remove log messages, you won’t get them confused for real print() calls.
If you just print to a log file, it’s easy to leave the log function calls in and just ignore them when you don’t need them. (You don’t have to constantly pull out print() calls.)
Using print is for coders with too much time on their hands. Use logging instead. Also, learn to use the Python debugger to debug bugs and Pylint to prevent bugs and make your code readable.
python
To figure out bugs in your code, you might put in print statements/print() calls to display the value of variables.
Don’t do this. Use the Python logging module.
The logging is better than printing because:
It’s easy to put a timestamp in each message, which is very handy.
You can have different levels of urgency for messages, and filter how less urgent messages.
When you want to later find/remove log messages, you won’t get them confused for real print() calls.
If you just print to a log file, it’s easy to leave the log function calls in and just ignore them when you don’t need them. (You don’t have to constantly pull out print() calls.)
Using print is for coders with too much time on their hands. Use logging instead. Also, learn to use the Python debugger to debug bugs and Pylint to prevent bugs and make your code readable.
25 days ago
How text editing on the iPad should be
28 days ago
RT @siracusa: I want this now: (via @danielpunkass)
from twitter
28 days ago
apple
AppleScript
arxiv
BBEdit
BibDesk
BibTeX
blog
career
coding
copyright
css
email
encryption
fonts
funny
genealogy
git
gnuplot
gps
grep
hosting
html
ipad
javascript
jekyll
kids
latex
maps
math
osx
politics
python
R
rsync
s3
science
scripts
search
security
shell
society
teaching
tikz
via:alexp
via:Boinside
via:drdrang
via:drstevo
via:igrigorik
via:jcsiegrist
via:macdrifter
via:mcdan
via:mountain
via:neurobashing
via:noahread
via:rtmfd
via:runawaycoder
via:Zettt
via:zts
video
web