Disqus - Latest Comments for jbalogh

Re: Logging Django Performance

jbalogh — Thu, 09 Jun 2011 19:42:05 -0000

Cool! I have some nasty scripts to dump the zamboni output into json for loading into highcharts, but it's always felt really hacky. I'm hoping to replace it with graphite sometime soon.

Re: http://ryansnyder.me/post/613194200

jbalogh — Wed, 19 May 2010 10:36:49 -0000

So I guess we'll see you on the Python side soon?

Re: Nose Test Runner for Django

jbalogh — Thu, 29 Oct 2009 11:24:37 -0000

I wrote a simpler nose_runner.py a while ago, and then some extra features got added that are now in basie's svn repo. When I created django-nose I forked it from that simpler version of nose_runner.py, so you might say that basie's is more mature. But django-nose tries to integrate better with django, and it's the one I use now on github and pypi, so I think django-nose is the one to go with.

Are you using django.test.TestCase to run your tests? The logic for creating and rolling back transactions is in that class, so I'm not sure how django-nose could affect that.

Re: Nose Test Runner for Django

jbalogh — Wed, 21 Oct 2009 11:05:06 -0000

I added a link at the top to the newer and better documented packages on pypi and github.

nose starts its recursive search for tests in the current directory, so it won't find any django tests unless you tell it to search wherever you have django installed.

Re: GitHub Ribbon Using CSS Transforms

jbalogh — Thu, 15 Oct 2009 18:53:57 -0000

Nice and simple! I started out with something like that, but it got more complicated as I ran into browser issues and then I got bored. :)

Re: The worst schema versioning system, ever?

jbalogh — Sun, 24 May 2009 11:22:02 -0000

I assume you're talking about Rails Migrations? Why aren't we using that? How easy is it to install?

Re: Managing Test Data

jbalogh — Thu, 25 Sep 2008 23:12:56 -0000

I love the template idea. That would make it easy to see the important parts of an object, ignoring all the noise. I'm not all about the __template__ vars, they're a bit ugly. What if each model had one template, which is automatically inherited when you're using this system?

I don't think you can get around writing the primary keys; how else are you going to link two models declaratively? Maybe you can just write them for models that need to be linked, and have the rest filled in magically? That could be a goal after you have the inheritance business working.

I'm against sharing fixtures, because your app shouldn't break when I change the fixtures in my app. But your final proposal doesn't mention that, just sharing templates. I'm ok with that.

Great idea! Is it ready to use yet? :-)

Re: Subversion headaches

jbalogh — Sun, 21 Sep 2008 17:52:15 -0000

Congrats on getting it working. :)

Re: Testing Django applications

jbalogh — Wed, 27 Aug 2008 21:05:35 -0000

If you search for nose on the pyrtl site, you'll see that I already proposed it, and Greg said yes. Hooray for nose and lightweight testing! Down with unittest!

Re: Basie search

jbalogh — Tue, 26 Aug 2008 17:44:00 -0000

Why wouldn't we want to reuse and extend one of the existing django(-)search apps?
http://code.google.com/p/dj... and http://code.google.com/p/dj...

These projects have pluggable backends and aim to be reusable.

Re: Basie search

jbalogh — Tue, 26 Aug 2008 17:39:09 -0000

Yikes! exec, toReturn? I can't look at this! :)

Re: Providing initial data for models

jbalogh — Tue, 26 Aug 2008 14:42:59 -0000

Greg said (and I agree):

I still like the following argument:

1. One data format (no matter which one) is better than several.

2. We’re going to use JSON for our REST API.

3. So we should use JSON for fixture data, config files, etc.