kennethlove

Yeah, that'll work. django-discover-runner is less invasive, IMO, though, and works really nicely with standard Django testing setups or more-package-oriented ones.

That's a 404.

I'd love a copy too, actually. Just the CSS. username @gmail.com as well, if you'd be so kind.

Every time this pops up, I just have to mention http://developerduck.com

Just started it up (personally), but I blog about...shit, don't really know yet. Likely programming, personal life (dad, husband, etc), and the like. http://blog.gigantuan.net

My professional blog, mostly about Python and Django, is at http://brack3t.com

I've added a link to subscribe to the mailing list to the top of the site.

Glad you found out what it was!

I'm running VirtualBox 4.2.4 but I would think, since it creates the VM when you `vagrant up`, that it wouldn't matter what version of VB you were running. So that's odd.

The Vagrant version I have is 1.0.5, just for completeness sake.

I just downloaded the zip file again to check, and there's nothing in there (at least that I can find) that mentions a version of VirtualBox. You're also the first person to mention a problem like this (one other person had a problem after running the VM with getting packages from Google).

You could try downgrading, or, since you're on a sane OS, just running everything sans VM. You'll need to install Git and PostgreSQL yourself, though.

Let me know if anything changes, please. I'll ask around and let you know if I find anything out.

Thanks, and sorry for your problems.

I thought I had one. I'll add it this evening.

Your browser should have a bookmark function...

When the official download comes out in a day or two, it'll have chapter markers in it for QuickTime, so you'll be able to jump around as needed.

The plan is to do 1-2 per month, ideally about 1 every 2 weeks. I have to do them in my (and my editor's) off time, so some months that may slip.

The Kickstarter is funding all 10 originally planned episodes plus ~5 more covering FAQ-type situations.

done

You're right. We had a staggered layout, a la Pinterest, until last week. Now that we've evened up everything, I'm sure we could remove Masonry. It's currently still using it, though.

Yes. We specify a height and width in the HTML and the CSS, but it's still nice to pay attention to the images' loaded status.

---There's no demo because it behaves exactly like the Masonry example for infinite scrolling and Pinterest.---

Screw it, I added a link to the example. It's on tindie.com.

I'm not even sure how to respond to this comment.

Django is a solid framework with tons of real-world example of that very fact. Rails is a fine framework, too, but it's in a language I don't enjoy and is, to me, no where near as elegant as Django (usually) is.

I'm also not sure I see the point is commenting on a post about a feature of a framework with, essentially "swap your entire stack over to my favorite language". Maybe you have some way to backup your statement?

Yeah, I'm (the author) a giant fan of CBVs in Django. Sadly, the form wizard views, although class-based and fairly sprawling, don't seem to be very friendly to experimentation. It seems to be a pretty locked-in workflow that's horribly undocumented. Hence the post.

Thanks, I do too! Glad you liked the first series.

I'd say at least a year. The outage what prompted my partner and I to build djangopeople.me.

Yeah, we have another post in the pipeline for exploring Tastypie, especially for a) using it with Backbone, and b) using it as a simple writable API for jQuery.

Django does seem to be fairly open-ended when it comes to AJAX, and while there may no be standard way to do it, I think approaches like we take are a lot more reliable than some of the others I've seen.

I whole-heartedly agree. I haven't had to deal with the provider side, but the consumer side is a bit of a nightmare too unless you're dealing ONLY with an established provider, like Twitter.

And the fact that, for ``python-oauth2``, the "2" refers to it being the second package.... Yeah, not happy the day I found that out.

Yeah, it is actually.

https://github.com/brack3t/django-braces is the Github repo, or you can ``pip install django-braces`` into your project. All the mixins are then imported from the ``braces`` package.

True, that does bring up an interesting point.

I'll have to give it another look later, maybe I'll change my mind.

No one should have to read the source to understand such a large and useful area of a framework.

That's similar to expecting people to read the source code to understand ActiveRecord or something.

I don't care for the decorator at all, but the MultipleFormView mixin looks very handy. Thanks.

That is a really nice syntax. I kind of like the specificity of ``form_valid`` (for example), though.

And, yes, our mixins are Django-only (hence the title!)

Also, why the ``set_test_cookie`` on every GET?

As the author, I think we're pretty much on the same page. My example of ``span6`` is from the Twitter Bootstrap (which is also available as Less).

I don't think tools like Less and Sass can save us from this decision, though. You can write hundreds of rules to handle different configurations of HTML elements and remain completely semantic, but eventually you'll have the same configuration in two places where you want them to appear different. Then you have the decision of giving one of them an ID or giving them classes and those have to be semantic (and custom to your site, requiring learning from future devs) or generic and breaking the "semantic all the things!!!" rule.

People are trying to figure this out. Semantic.gs is a great example of that. I just don't see, in our current browser, markup, and styles situation, a way to avoid generic classes that's still new-developer-friendly.

django-social-auth is the best for doing Facebook authentication/account-creation.

I don't deal with the Graph API much so I can't comment on that aspect.

I can't really answer that since I don't work for MailChimp.

The OAuth2 service is aimed at people building apps for people that use MailChimp, not people that subscribe to a mailing list hosted on MailChimp.

Like how you'd use Twitter's OAuth2 service to build apps for people that use Twitter, not those that just read feeds.