Re: Actively developed/supported piston fork?

[reduxionist]

On Thursday, October 30, 2014 4:34:32 PM UTC+7, sams...@gmail.com wrote:
>
> I've inherited an app that was written for Django 1.4, and updated it to 
> Django 1.7.
> ...
> Are any being actively used/fixed/supported?  Which one should I try?
>

While Russell Keith-Magee is definitely correct when he says "the bulk of 
the energy around REST tools in the Django community has moved to Django 
REST Framework," given that you have inherited legacy code, the good news 
is that there are indeed active forks of 
Piston, thanks to how widely used it was before the advent of DRF 
fore-runner TastyPie. The most recently active fork I know of is: 
https://github.com/matllubos/django-piston, which is currently actively 
maintained. If that doesn't work for you for any reason, let me know and 
I'll dig up my other, next-most-recently-active, Piston forks…

Best wishes,
Jonathan Barratt

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3ef0628f-fe4e-4186-ad74-b6906043f24e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Actively developed/supported piston fork?

[Russell Keith-Magee]

Hi,

On Thu, Oct 30, 2014 at 5:34 PM,  wrote:

> I've inherited an app that was written for Django 1.4, and updated it to
> Django 1.7.
>
> I've noticed lots of forks of Piston on the web.
>
> Are any being actively used/fixed/supported?  Which one should I try?
>
> Is anyone who has a fork that they are keeping up to date on this mailing
> list?
>
> Finally - if it makes more sense to replace piston with something else,
> what would be the easiest thing to replace it with?
>
> Thanks!
>

I'm not aware of any actively maintained fork of Piston. The bulk of the
energy around REST tools in the Django community has moved to Django REST
Framework:

http://www.django-rest-framework.org

It's not a drop-in replacement for Piston, though - you'll need to do some
re-engineering.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAJxq84-p_MvcpCeJmcCSM-fP%3DVJsddd%3D-S16%3DGhu%2BZRiaqn4Hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Actively developed/supported piston fork?

[samslists]

I've inherited an app that was written for Django 1.4, and updated it to 
Django 1.7.

I've noticed lots of forks of Piston on the web.

Are any being actively used/fixed/supported?  Which one should I try?

Is anyone who has a fork that they are keeping up to date on this mailing 
list?

Finally - if it makes more sense to replace piston with something else, 
what would be the easiest thing to replace it with?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1e471923-8cf2-4691-af0a-a99788b13bab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.