Must-have Django packages • Hacker News Board

Re: Must-have Django packages

#71

Post by huxley » Thu, Jan 09, 2014, 9:35 PM UTC

japhyr wrote: post #65

famousactress wrote: post #63

Notable omission of South ( http://south.aeracode.org/ )

I think that's because South has been rolled into Django now. Is that correct?

Close, but not exactly, Andrew Godwin, the creator of South, has added support for migrations into the dev branch of Django, to be part of the Django 1.7 release.

https://docs.djangoproject.com/en/dev/topics/migrations/

Andrew has significantly rethought migrations and applied the lessons he's learned from years of maintaining and developing South.

He's kept a developer diary that has been pretty fascinating to read (YMMV):

http://www.aeracode.org/2013/11/27/new-apps-migrations/

and others at:

http://www.aeracode.org/category/django-diaries/

[update: route3 is faster than me, but still it's worth checking out the developer diaries]

Re: Must-have Django packages

#72

Post by bmelton » Thu, Jan 09, 2014, 9:49 PM UTC

dkoch wrote: post #13

I've found django-allauth a bit friendlier than django-social-auth, and it covers registration of local accounts in one package.

Oddly enough, django-social-auth has been deprecated for some time now in favor of python-social-auth[1] (same author). It is more user friendly than django-social-auth, and also offers up a lot more functionality that django-social-auth wasn't giving me.

[1] - https://github.com/omab/python-social-auth

Re: Must-have Django packages

#73

Post by glynjackson » Thu, Jan 09, 2014, 9:50 PM UTC

A few I work with on most projects are...

Backend: one of the most popular API Frameworks is Tastypie. Authentication and authorization: Django Userena. Debugging: Django Extensions. Django CMS Django Haystack

These are a must for your tool kit.

Re: Must-have Django packages

#74

Post by glynjackson » Thu, Jan 09, 2014, 9:52 PM UTC

japhyr wrote: post #65

famousactress wrote: post #63

Notable omission of South ( http://south.aeracode.org/ )

I think that's because South has been rolled into Django now. Is that correct?

No, still use South everyday and will until it's rolled out in Django 1.7 - fingers crossed!

Re: Must-have Django packages

#75

Post by timc3 » Thu, Jan 09, 2014, 9:58 PM UTC

glynjackson wrote: post #73

A few I work with on most projects are... Backend: one of the most popular API Frameworks is Tastypie. Authentication and authorization: Django Userena. Debugging: Django Extensions. Django CMS Django Haystack These are a must for your tool kit.

I would recommend DjangoRestFramework any day over Tastypie after having used Tastypie for two years.

DjangoRestFramework code base is better, it's better thought out, it should be part of Django core.

Re: Must-have Django packages

#76

Post by oinksoft » Thu, Jan 09, 2014, 10:25 PM UTC

falcolas wrote: post #12

Interesting, my fairly large django project uses none of those. Instead, the addons we consider to be critical are these these: django-debreach django-redis jinja2 pytz Redis for queues and caching, debreach to secure the CSRF tokens and vary your content length to avoid the BREACH vulnerability. jinja2 for doing templates outside of returning data, and pytz so you can use timezones in your data models. I also recomm…

pytz probably doesn't belong in a discussion of Django libraries. It's needed by pretty much any Python program that works with localized datetimes.

  > jinja2 for doing templates outside of returning data

What do you mean?

Re: Must-have Django packages

#77

Post by aidos » Thu, Jan 09, 2014, 10:27 PM UTC

mixmastamyk wrote: post #59

true_religion wrote: post #58

Earlier quoted context omitted.

If you're doing a lot of # crunching, you might try using Cython for those bits. You can get a 10x speedup without changing semantics and just annotating types.

Thanks for the tip. Most of it is done by python-dateutil though so I think it in C already. I'm basically checking ~500 recurring events to see if they occur today with django-schedule.

Oooow. Interesting one. So the events can be on different schedules / frequencies? It sounds like something you should be able to do with a single sql query. Could you provide a bit more info?

Re: Must-have Django packages

#78

Post by aikii » Thu, Jan 09, 2014, 11:54 PM UTC

Cripsy forms, because simple things like adding the necessary markup for bootstrap to forms is super-boring otherwise ; in general, it helps with custom form layout, which is usually a template maintenance hell

https://github.com/maraujop/django-crispy-forms

Re: Must-have Django packages

#79

Post by ericd » Fri, Jan 10, 2014, 12:19 AM UTC

huxley wrote: post #71

japhyr wrote: post #65

Earlier quoted context omitted.

I think that's because South has been rolled into Django now. Is that correct?

Close, but not exactly, Andrew Godwin, the creator of South, has added support for migrations into the dev branch of Django, to be part of the Django 1.7 release. https://docs.djangoproject.com/en/dev/topics/migrations/ Andrew has significantly rethought migrations and applied the lessons he's learned from years of maintaining and developing South. He's kept a developer diary that has been pretty fascinating to read…

For a greenfield app, would you recommend starting with 1.7, or do you think it will be simple enough to convert from South that it's not worth it? (I have no idea how stable 1.7 is)

Re: Must-have Django packages

#80

Post by natmaster » Fri, Jan 10, 2014, 12:38 AM UTC

waterlion wrote: post #16

natmaster wrote: post #6

Earlier quoted context omitted.

The APIs are more sane. Added bonus of a cool HTML api explorer view.

How do you square that with the article? It specifically says that that Django REST is "insane".

The word insane does not appear on the page