Hey, thanks for stopping by.
You’ve stopped by really early. But I’m glad you did.
Really, there is going to be some great information here, I just haven’t written it yet.
I could have waited to go live with the site until I had lots of content up.
But I didn’t.
I decided to go live very fast, and then add content.
Please check out the about page to see what sorts of posts you will see here.
If that sounds like something interesting, please sign up to receive posts by email.
Right now I’m using feedburner to manage this.
When I get a proper newsletter set up, I’ll let you know.
I don’t even have a privacy page set up yet.
But when I do, it will say something like “I won’t sell or give away your email, blah blah blah, and I’m not going to try to sell you anything via the email list, etc.” Except if I come up with something to sell… I don’t have anything yet. Maybe an ebook or something. But there’s nothing yet so don’t worry. And even if I did, I’m not going to spam your inbox. I just don’t have time. And I don’t like it when people do that to me.
- How do I start testing?
- pytest session scoped fixtures
- Who is this guy anyway?
- pytest fixtures nuts and bolts
- pytest fixtures easy example
- pytest xUnit style fixtures
- pytest fixtures – part 1
- pytest full support of unittest fixtures in pytest 2.4
- Sublime Text block/column copy/paste
- The power of “Thank You”
- Block cursor in ST3
- nose fixture reference
- tip: dictionary get() works like getattr
- New Start Here page
- I’m annoyed with Python’s ternary operator
- If unittest is wrong, nose is wrong also
- Perhaps unittest is wrong, and tearDown should always run
- Reworking categories
- pytest support for unittest style fixtures
- nose support for unittest style fixtures
- Run a single test class with unittest, nosetests, py.test
- What happens when unittest fixtures fail
- unittest fixture syntax and flow reference
- for pip proxy, use dev instead of 1.3.1
- How not to test, part 1
- pytest debug print logging in real time
- regex search and replace example scripts
- Markdown.py passes first 3 tests
- nose introduction
- pytest introduction
- Confession … I still use perl on the command line
- unittest introduction
- tip: interactive python from cygwin when using windows python install
- Poll Results: test frameworks
- doctest introduction
- Poll: Which test frameworks are you most interested in?
- Contact form fixed
- Software API/CLI interface adapters
- Kivy looks promising for cross platform UI
- Stub for markdown.py
- Markdown.py requirements
- Markdown.py on github
- Why Markdown
- Why is this empty?
- Initial post