HN user

dnsauve

37 karma

[ my public key: https://keybase.io/notanumber; my proof: https://keybase.io/notanumber/sigs/nTS4Wc00-rZSWXgC2iXGE7vomzvci6xe9l7kPcw-Y7k ]

Posts3
Comments8
View on HN

I don't see why this isn't good advice.

This is exactly what I did when I was trying to decide between the two. It really doesn't take long to work your way through the introductory tutorials to get a feel for which framework and language you prefer.

Count me in as another lost customer. They were even calling me to try and upsell their service to the point where I started avoiding their calls.

The whole thing just felt so high pressure, spammy that I'd rather not deal with them anymore.

Yes, please. I am very interested in this. I feel as though I've only scratched the surface of what ST2 can do even though I've been using it for the last year and experimented with writing my own plugins.

I'd also love to see a "cheat-sheet" for shortcut keys.

While I love the idea of homeschooling and unschooling, I can't quite figure out how people do this while still managing to pay their bills. Wouldn't this, in essence, take up a significant portion of your day, preventing you from working?

Django and Python 3 17 years ago

Anyone else confused by this opening statement: "Python 3 has been out for about a year at this point, and so far Django hasn't really started to move towards it (at least at a first glance). However, Django has already begun the long process towards moving to Python 3[...]"?

One way I've always dealt with the repetitive bits in my tests is to break out the offending code into separate utility type methods that can then be called by the test itself (or even multiple tests) as needed.

These methods could themselves also contain assertThis, assertThat, as needed to ensure they're functioning as expected as well.

Another way I've done it is to have tests calling other test methods themselves. i.e., something like:

    testFoo(self):
       # Do some test here.
       self.assertTrue(....)

    testBar(self):
       # Test that Foo works for logged in user as well
       self.client.login(username='joe', password='abc')
       self.testFoo()
       self.assertTrue(...)

Thanks for the encouragement. This is my first open source project, and I mainly wrote it because I was disappointed with Djapian's Xapian interface and was quite impressed with Haystack.

Originally, I was planning on using Whoosh for the backend, but quickly ran into issues with locked files when deploying to a live server.

Anyways, I'd love to hear any comments and feedback you may have after you've given the code a try.