5 ms·

Django REST framework 3.0

255 points by tomchristie 12y ago

chatmasta 12y ago
Awesome! Great job Tom. DRF is one of those open source projects that makes me wonder how one person can be so productive. I'm a big fan of the new serializers. Personally I'll probably stick with my custom flask tooling since it works better for 100-200 line microservices, but I'll definitely be trying out this latest DRF release. I'm sure this is the last thing you want to be hearing right now, but any updates on the flask counterpart you were working on? :) are you abandoning that while you work on 3.1 and 3.2? Or altogether?
- tomchristie 12y ago
  Flask API is certainly on pause while 3.1 and 3.2 are addressed yes. After that it depends on what I feel is the most productive use of my time. Perhaps general purpose Python API tooling, that includes Flask as one of the options, or perhaps work on hypermedia stuff that I've got in my head.
  - chatmasta 12y ago
    I like the sound of general purpose API tooling! In developing small services with flask, I've found myself reusing the same serialization code, input validation code, etc. You might be interested in Marshmallow, a minimalist serializtion framework. [0] I've enjoyed working with it, especially with Flask. I believe Flask-Restless or Flask-Restful uses it as well. [0] http://marshmallow.readthedocs.org/en/latest/ http://marshmallow.readthedocs.org/en/latest/
    - joshfriend 12y ago
      Flask-RESTful currently has its own serializer module, but we have plans to deprecate it in the future and replace it with Marshmallow[1] [1]: https://github.com/flask-restful/flask-restful/issues/335 https://github.com/flask-restful/flask-restful/issues/335
      - boronine 12y ago
        I'm developing a system that, among other things, could be an even more minimalist alternative to Marshmallow [0]. I actually haven't seen Marshmallow until now, it looks very nice. [0] http://teleport-json.org/ http://teleport-json.org/
citadelgrad 12y ago
While I don't have any plans to upgrade my use of the DRF, I supported this project at the advocate level because I'm so thankful to have tools like this available. Thanks again Tom for all your hard work.
gregthompsonjr 12y ago
Woo!
- max55 12y ago
  Amazing stuff, and very exciting
aidos 12y ago
Congrats @tomchristie (and all those involved). DRF is the only thing that ever makes me jealous of Django.
makaimc 12y ago
Tom, congratulations! This is exceptional work. It's exciting to see this release come to fruition via your Kickstarter campaign and a whole lot of work on your part along with the Django community.
bigsassy 12y ago
I'm loving this Kickstarter model for major open source software. Just in the Django community we're getting incredibly high quality work between migrations in Django 1.7, Django REST Framework 3.0, and the PostgreSQL extensions Kickstarters. I've only been paying attention to the Django world with these Kickstarters, but is this catching on in any other sphere of software development (Ruby, Java, .NET)?
- yen223 12y ago
  Agreed about the Kickstarter model for open-source software. It's the best of both worlds - developers can contribute to the community while still getting paid for it.
- danielsamuels 12y ago
  There was recently an Indiegogo project for improving the template engine in Django too.
  - tragic 12y ago
    The main thing is to make them swappable, which will be great: https://www.indiegogo.com/projects/multiple-template-engines-for-django https://www.indiegogo.com/projects/multiple-template-engines...
- Argorak 12y ago
  Ruby had at least three: https://www.bountysource.com/fundraisers/489-rvm-2-0 https://www.bountysource.com/fundraisers/489-rvm-2-0 https://www.bountysource.com/teams/virtus/fundraiser https://www.bountysource.com/teams/virtus/fundraiser https://www.kickstarter.com/projects/1397300529/railsapp/posts https://www.kickstarter.com/projects/1397300529/railsapp/pos...
- gtaylor 12y ago
  From a business perspective, chipping into a Django kickstarter headed up by someone like Tom is an investment with an incredibly high chance to return something valuable. In this case, Tom exceeded expectations with an excellent 3.0 release. We are going to save some developer time, improve the quality of our code, and be better equipped to handle whatever unexpected needs the future throws at us. Ditto for Andrew's Django migrations project. I hope we can all continue to show strong support for these projects, regardless of the ecosystem in question (Django, Rails, etc). We all come out ahead, as long as we make sure that the project leader has a good chance of delivering.
DodgyEggplant 12y ago
Congrats. Any recommended resources for experienced django dev on beginning with mobile/REST on django/iOS ?
harel 12y ago
Well done, congratulations. Are there any plans to continue the Flask port of the framework?
- tomchristie 12y ago
  I'm not sure at the moment, we'll see once the remaining bits of the kickstarter work (releases 3.1 and 3.2) are done and released.
paulhallett 12y ago
Congratulations Tom. This trend of crowdfunding development for Django and Python projects should be copied by other communities. It's amazing how much high quality work is coming out of it.
e12e 12y ago
Congratulations! Any update on how the money was spent? I found: https://www.kickstarter.com/projects/tomchristie/django-rest-framework-3/posts/921581 https://www.kickstarter.com/projects/tomchristie/django-rest... and that all sounds very reasonable. Personally[1] I wouldn't mind the dev(s) just pocketing the money -- but was there an update on "budget"? [1] One might quip that that's easy to say, as I didn't back this particular project. I've backed a few other KSs, though -- and I can say that in all of those, I've/I'd generally been happy if the originators(?) kept any extra money (as long as the delivered on the goals, of course)
- jdimov 12y ago
  So why are you asking?
- philipn 12y ago
  Seems pretty clear from that linked post: Tom is going to use/used the money to support his time spent working on the project. And extra funds will be used/have been used to devote more time than he'd otherwise be able to spend.
- tomchristie 12y ago
  > Any update on how the money was spent? So this is only 1/3 of the Kickstarter to date. The two stretch goals are planned as releases 3.1 and 3.2. We were significantly overfunded, and I'll treat the extra time/budget flexibly depending on whatever seems highest priority, but it's mostly going towards ensuring I've got headroom for keeping the quality bar super high. (Plus extra time available for general support, triage, etc...) For transparency I plan to be ending up with treating 10% of the amount received as profit - the rest of the funding is simply covering the costs for the time I'm not working on client projects at DabApps (minus Kickstarter's cut and some taxes of course). I probably won't give a full time-spent breakout of how long each task has taken, I've not had requests from backers to do that, and not doing so frees me up to spend it however I think best without feeling like I need to justify things on a blow-by-blow basis.
  - e12e 12y ago
bestpcinfos 12y ago
I really appreciate it. DRF is awesome.
tuyguntn 12y ago
Great job, congratulations!!! Since author is here, would like to ask quick question, does this version support saving m2m relation data and, if yes,how does it handle failed related model saving, does it uses transaction at the beginning of request?
- tomchristie 12y ago
  Yes it does, but probably best to take this sort of thing onto the discussion group... https://groups.google.com/forum/#!forum/django-rest-framework https://groups.google.com/forum/#!forum/django-rest-framewor...

255 points by tomchristie 12y ago

Awesome! Great job Tom. DRF is one of those open source projects that makes me wonder how one person can be so productive. I'm a big fan of the new serializers. Personally I'll probably stick with my custom flask tooling since it works better for 100-200 line microservices, but I'll definitely be trying out this latest DRF release. I'm sure this is the last thing you want to be hearing right now, but any updates on the flask counterpart you were working on? :) are you abandoning that while you work on 3.1 and 3.2? Or altogether?

tomchristie 12y ago
Flask API is certainly on pause while 3.1 and 3.2 are addressed yes. After that it depends on what I feel is the most productive use of my time. Perhaps general purpose Python API tooling, that includes Flask as one of the options, or perhaps work on hypermedia stuff that I've got in my head.
- chatmasta 12y ago
  I like the sound of general purpose API tooling! In developing small services with flask, I've found myself reusing the same serialization code, input validation code, etc. You might be interested in Marshmallow, a minimalist serializtion framework. [0] I've enjoyed working with it, especially with Flask. I believe Flask-Restless or Flask-Restful uses it as well. [0] http://marshmallow.readthedocs.org/en/latest/ http://marshmallow.readthedocs.org/en/latest/
  - joshfriend 12y ago
    Flask-RESTful currently has its own serializer module, but we have plans to deprecate it in the future and replace it with Marshmallow[1] [1]: https://github.com/flask-restful/flask-restful/issues/335 https://github.com/flask-restful/flask-restful/issues/335
    - boronine 12y ago
      I'm developing a system that, among other things, could be an even more minimalist alternative to Marshmallow [0]. I actually haven't seen Marshmallow until now, it looks very nice. [0] http://teleport-json.org/ http://teleport-json.org/

citadelgrad 12y ago

While I don't have any plans to upgrade my use of the DRF, I supported this project at the advocate level because I'm so thankful to have tools like this available. Thanks again Tom for all your hard work.

gregthompsonjr 12y ago

Woo!

max55 12y ago
Amazing stuff, and very exciting

aidos 12y ago

Congrats @tomchristie (and all those involved). DRF is the only thing that ever makes me jealous of Django.

makaimc 12y ago

Tom, congratulations! This is exceptional work. It's exciting to see this release come to fruition via your Kickstarter campaign and a whole lot of work on your part along with the Django community.

bigsassy 12y ago

I'm loving this Kickstarter model for major open source software. Just in the Django community we're getting incredibly high quality work between migrations in Django 1.7, Django REST Framework 3.0, and the PostgreSQL extensions Kickstarters. I've only been paying attention to the Django world with these Kickstarters, but is this catching on in any other sphere of software development (Ruby, Java, .NET)?

yen223 12y ago
Agreed about the Kickstarter model for open-source software. It's the best of both worlds - developers can contribute to the community while still getting paid for it.
danielsamuels 12y ago
There was recently an Indiegogo project for improving the template engine in Django too.
- tragic 12y ago
  The main thing is to make them swappable, which will be great: https://www.indiegogo.com/projects/multiple-template-engines-for-django https://www.indiegogo.com/projects/multiple-template-engines...
Argorak 12y ago
Ruby had at least three: https://www.bountysource.com/fundraisers/489-rvm-2-0 https://www.bountysource.com/fundraisers/489-rvm-2-0 https://www.bountysource.com/teams/virtus/fundraiser https://www.bountysource.com/teams/virtus/fundraiser https://www.kickstarter.com/projects/1397300529/railsapp/posts https://www.kickstarter.com/projects/1397300529/railsapp/pos...
gtaylor 12y ago
From a business perspective, chipping into a Django kickstarter headed up by someone like Tom is an investment with an incredibly high chance to return something valuable. In this case, Tom exceeded expectations with an excellent 3.0 release. We are going to save some developer time, improve the quality of our code, and be better equipped to handle whatever unexpected needs the future throws at us. Ditto for Andrew's Django migrations project. I hope we can all continue to show strong support for these projects, regardless of the ecosystem in question (Django, Rails, etc). We all come out ahead, as long as we make sure that the project leader has a good chance of delivering.

DodgyEggplant 12y ago

Congrats. Any recommended resources for experienced django dev on beginning with mobile/REST on django/iOS ?

harel 12y ago

Well done, congratulations. Are there any plans to continue the Flask port of the framework?

tomchristie 12y ago
I'm not sure at the moment, we'll see once the remaining bits of the kickstarter work (releases 3.1 and 3.2) are done and released.

paulhallett 12y ago

Congratulations Tom. This trend of crowdfunding development for Django and Python projects should be copied by other communities. It's amazing how much high quality work is coming out of it.

e12e 12y ago

Congratulations! Any update on how the money was spent? I found: https://www.kickstarter.com/projects/tomchristie/django-rest-framework-3/posts/921581 https://www.kickstarter.com/projects/tomchristie/django-rest... and that all sounds very reasonable. Personally[1] I wouldn't mind the dev(s) just pocketing the money -- but was there an update on "budget"? [1] One might quip that that's easy to say, as I didn't back this particular project. I've backed a few other KSs, though -- and I can say that in all of those, I've/I'd generally been happy if the originators(?) kept any extra money (as long as the delivered on the goals, of course)

jdimov 12y ago
So why are you asking?
philipn 12y ago
Seems pretty clear from that linked post: Tom is going to use/used the money to support his time spent working on the project. And extra funds will be used/have been used to devote more time than he'd otherwise be able to spend.
tomchristie 12y ago
> Any update on how the money was spent? So this is only 1/3 of the Kickstarter to date. The two stretch goals are planned as releases 3.1 and 3.2. We were significantly overfunded, and I'll treat the extra time/budget flexibly depending on whatever seems highest priority, but it's mostly going towards ensuring I've got headroom for keeping the quality bar super high. (Plus extra time available for general support, triage, etc...) For transparency I plan to be ending up with treating 10% of the amount received as profit - the rest of the funding is simply covering the costs for the time I'm not working on client projects at DabApps (minus Kickstarter's cut and some taxes of course). I probably won't give a full time-spent breakout of how long each task has taken, I've not had requests from backers to do that, and not doing so frees me up to spend it however I think best without feeling like I need to justify things on a blow-by-blow basis.
- e12e 12y ago

bestpcinfos 12y ago

I really appreciate it. DRF is awesome.

tuyguntn 12y ago

Great job, congratulations!!! Since author is here, would like to ask quick question, does this version support saving m2m relation data and, if yes,how does it handle failed related model saving, does it uses transaction at the beginning of request?

tomchristie 12y ago
Yes it does, but probably best to take this sort of thing onto the discussion group... https://groups.google.com/forum/#!forum/django-rest-framework https://groups.google.com/forum/#!forum/django-rest-framewor...