Django REST framework 3.1 released • Hacker News Board

Re: Django REST framework 3.1 released

#11

Post by bliti » Fri, Mar 06, 2015, 3:47 PM UTC

tomchristie wrote: post #8

bliti wrote: post #5

@OP: What is your long term vision for the project? Reason I ask is due to how django keeps (IMO) gaining territory on the corporate and/or business stack. I get requests for support and new development consistently from companies in different markets/regions.

Broadly, we aiming for it to be a mature, sustainable and well-supported general purpose Web API framework. We tend to be fairly aggressive about keeping the scope manageable in order to keep to that. For example 3.1 moves some functionality out into third party packages, so that we can concentrate on the quality of the core framework. Some of the longer term feature work: * Admin style interface - See https://www.ki…

Thank you.

Re: Django REST framework 3.1 released

#12

Post by chucksmash » Fri, Mar 06, 2015, 3:49 PM UTC

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely.

What are the plans (if any) for continued development on Flask-API?

Re: Django REST framework 3.1 released

#13

Post by tomchristie » Fri, Mar 06, 2015, 3:51 PM UTC

Alex3917 wrote: post #10

jnbiche wrote: post #4

Just wanted to say that this is one of the most beautifully-documented projects I've ever used. Bravo!

Agreed, although I wish there was more documentation on the benefits of each feature, rather than just how to implement it. E.g. there are dozens of pages on how to implement serializers, which is great, but the section on the benefits of serializers is only a paragraph or two long. So after reading all the documentation I'm still unclear as to the best practices on when vs when not to use them, and what the best pra…

Thanks Alex, I think that's a great point.

Please do feel free to follow this up by raising an issue on the repository - it'd be good to talk through some specifics about areas to improve.

Re: Django REST framework 3.1 released

#14

Post by tomchristie » Fri, Mar 06, 2015, 3:57 PM UTC

chucksmash wrote: post #12

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?

At the moment it's on hold - I certainly won't be doing anything with Flask until the Kickstarter work is all complete. I'm undecided after that.

It'd be interesting to get your opinion on what your take would be on using Django/Django REST framework if it had decent built-in support for use with SQLAlchemy.

Re: Django REST framework 3.1 released

#15

Post by vosper » Fri, Mar 06, 2015, 4:00 PM UTC

chucksmash wrote: post #12

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?

I'm curious why you decided to move APIs from Django to Flask? We've built our APIs on Flask, and, though I like Flask a lot, the major complaint is that there's no real story around user authentication and authorization, endpoint versioning, and a handful of other things that aren't directly serving the purpose of the API, but are important nonetheless.

There are a hodge-podge of plugins to do various things, but they don't necessarily share the same design principles or work well together. Some are so abstracted that by the time you've got a concrete implementation you could have just rolled your own.

EDIT: Grammar, added a sentence.

Re: Django REST framework 3.1 released

#16

Post by brento » Fri, Mar 06, 2015, 4:04 PM UTC

chucksmash wrote: post #12

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?

I'm curious why the choice was made to switch to Flask?

Re: Django REST framework 3.1 released

#17

Post by [deleted] » Fri, Mar 06, 2015, 4:08 PM UTC

tomchristie wrote: post #8

bliti wrote: post #5

@OP: What is your long term vision for the project? Reason I ask is due to how django keeps (IMO) gaining territory on the corporate and/or business stack. I get requests for support and new development consistently from companies in different markets/regions.

Broadly, we aiming for it to be a mature, sustainable and well-supported general purpose Web API framework. We tend to be fairly aggressive about keeping the scope manageable in order to keep to that. For example 3.1 moves some functionality out into third party packages, so that we can concentrate on the quality of the core framework. Some of the longer term feature work: * Admin style interface - See https://www.ki…

[deleted]

Re: Django REST framework 3.1 released

#18

Post by wylee » Fri, Mar 06, 2015, 4:10 PM UTC

the_vincedent wrote: post #2

Still no M2M for ModelSerializer..? Guess I'll have to just keep using a ton of shitty hacks.

I'm not sure what your use case is, but you may want to look at serializers.RelatedField.

Re: Django REST framework 3.1 released

#19

Post by aidos » Fri, Mar 06, 2015, 4:11 PM UTC

tomchristie wrote: post #14

chucksmash wrote: post #12

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?

At the moment it's on hold - I certainly won't be doing anything with Flask until the Kickstarter work is all complete. I'm undecided after that. It'd be interesting to get your opinion on what your take would be on using Django/Django REST framework if it had decent built-in support for use with SQLAlchemy.

EDIT this conversation came up while I was writing this comment on another thread. Some of my questions have already been answered so I've reworded it.

Said it before, and I'll say it again - DRF is one of the few things that makes me wish I was on Django.

Is the newer DRF code abstracted nicely to make a port to Flask easier?

It's something I actually looked at doing myself a year ago but there looked to be a lot of effort involved.

I often look at projects that are Django-this or Flask-that and think to myself - this could be a nice clean agnostic library with layers for which ever framework. Often by that stage it's too late, everything is too embedded.

In this case, I guess that DRF intrinsically deals with the framework specific layers a lot so it's probably necessarily tightly bound.

Re: Django REST framework 3.1 released

#20

Post by chucksmash » Fri, Mar 06, 2015, 4:17 PM UTC

brento wrote: post #16

chucksmash wrote: post #12

Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?

I'm curious why the choice was made to switch to Flask?

We use both. I came in with a preference for Django but the applications we build are generally talking to legacy data stores so we more or less lose the Django ORM right off the bat. That cancels out a lot of the advantages Django has, unfortunately.