Must-have Django packages

#1

Post by rule30 » Thu, Jan 09, 2014, 3:33 PM UTC

Must-have Django packages
devcharm.com

Re: Must-have Django packages

#2

Post by porter » Thu, Jan 09, 2014, 4:31 PM UTC

What about South?

Re: Must-have Django packages

#3

Post by collyw » Thu, Jan 09, 2014, 4:42 PM UTC

I currently use Tasypie.

Would I gain anything switching to Django REST framework?

Re: Must-have Django packages

#4

Post by rule30 » Thu, Jan 09, 2014, 4:43 PM UTC

porter wrote: post #2

What about South?

Have a go at editing the `Utils` section.

Re: Must-have Django packages

#5

Post by edanm » Thu, Jan 09, 2014, 4:50 PM UTC

collyw wrote: post #3

I currently use Tasypie. Would I gain anything switching to Django REST framework?

We switched form Tastypie over to Django REST Framework, and are overall pretty happy. Cleaner, clearer code that's easier to work with.

Plus, it generates a browsable api that you can explore via the web, without any extra work. Which makes life a lot easier, believe me.

Re: Must-have Django packages

#6

Post by natmaster » Thu, Jan 09, 2014, 4:52 PM UTC

collyw wrote: post #3

I currently use Tasypie. Would I gain anything switching to Django REST framework?

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

Re: Must-have Django packages

#7

Post by michaelmior » Thu, Jan 09, 2014, 5:04 PM UTC

"Must-have" anything always feels like clickbait to me.

Re: Must-have Django packages

#8

Post by polpetta » Thu, Jan 09, 2014, 5:07 PM UTC

michaelmior wrote: post #7

"Must-have" anything always feels like clickbait to me.

Eh, Internet is based on clickbaits and lolcats. $ad but true.

Re: Must-have Django packages

#9

Post by cheshire137 » Thu, Jan 09, 2014, 5:07 PM UTC

michaelmior wrote: post #7

"Must-have" anything always feels like clickbait to me.

Just reminds me of scummy in-your-face ads everywhere, like at a mall or in a women's magazine.

Re: Must-have Django packages

#10

Post by gmu3 » Thu, Jan 09, 2014, 5:09 PM UTC

porter wrote: post #2

What about South?

I agree South should probably make the list although database migrations have finally made their way into the Django core so perhaps that's why the author didn't mention South.