tomchristie

15 ms·

91.
by tomchristie 12y ago
Sure, yes. In Python land for example Django and Flask both present the request parameters in a dictionary-like data structure that supports lookup of the complete list of values passed for a given name. Regular lookups will give you just a
92.
by tomchristie 12y ago
JSON Pointer isn't quite the same thing.
93.
by tomchristie 12y ago
Seems pretty decent. Also neat that the nesting style could be repurposed to support nested structures in regular form-encoded HTML forms. Main limitation on actually being able to use this is that `GET` and `POST` continue to be the only
94.
by tomchristie 12y ago
Think that's fair point, yup. Very easy to do unintentionally, and it's non-intuitive that it'll suddenly change the return type. It's not clear if this style is really necessary. Why not just use the indexed syntax in t
95.
Django models, encapsulation and data integrity(dabapps.com)
2 points by tomchristie 12y ago|0 comments
96.
by tomchristie 12y ago
Hiya, I've just removed the limits on the higher levels of backing. See the 'Day 1 - Funded!' update here... https://www.kickstarter.com/projects/tomchristie/django-rest... - There's been so mu
97.
Kickstarting Django REST framework 3(django-rest-framework.org)
4 points by tomchristie 12y ago|0 comments
98.
Django REST framework 3(kickstarter.com)
310 points by tomchristie 12y ago|72 comments
99.
by tomchristie 12y ago
I find having a live preview really gives me a better feel for the flow of the document. I love Markdown for it's simplicity, but that doesn't mean I only ever want to see it rendered in plain text.
100.
by tomchristie 13y ago
So ignoring the hype, here's the outcome-to-date... The ticket was reconsidered, reopened and classified as a bug. http://bugs.python.org/msg212771 Nick Coghlan's dissection of the issue here: https://m
101.
by tomchristie 13y ago
Quite an endorsement; I'll have to try to make the time to check that out properly. :)
102.
by tomchristie 13y ago
They don't need too, but it sure-as-hell improves accessibility & usability.
103.
by tomchristie 13y ago
> one example returns json array, what about JSON venerability? Side point: I don't have a reference for this, but from what I understand the JSON array vulnerability has long since been closed in all sane browsers.
104.
by tomchristie 13y ago
> Any dates for 1.0 release? If anyone wants to give me a coupla days paid work on this, then yah I'm sure that could be arranged. :)
105.
by tomchristie 13y ago
Most welcome! For anyone on this thread who's interested in contributing I'd suggest opening a ticket citing your interest, so that we've then go a place we can start the discussion from.
106.
by tomchristie 13y ago
Built in pagination isn't something that's planned atm, tho typically I'd always return objects as the top level representation, and embed the pagination links inside that.
107.
by tomchristie 13y ago
Looks nice. I am considering factoring the core of both Flask API and Django REST framework out into a library that could be integrated with any Python web framework - But that's not going to happen right away, so probably not much use
108.
by tomchristie 13y ago
The most obvious feature difference is the browsable API. Flask API also shares the same architecture as the core of Django REST framework, which I think just has a really nice separation of concerns. Also the interface of `request.data` me
109.
by tomchristie 13y ago
> It should be straightforward to use a decorator to protect restricted pages. Authentication policies will use a similar style to the renderers and parsers (and all of REST framework). You'll be able to set them per-view with a de
110.
Flask API – Browsable Web APIs for Flask(flaskapi.org)
171 points by tomchristie 13y ago|48 comments
111.
by tomchristie 13y ago
No, I understand why you might want a digital version. What I don't understand is why you think you're entitled to a digital version. These are two independent authors making their own informed decision about which medium they
112.
by tomchristie 13y ago
I don't really understand this point of view. If you'd prefer not to purchase their book then that's cool - but only Audrey and Daniel are in a position to assess if it was worth their effort to publish an ebook or not, surel
113.
by tomchristie 13y ago
If you want a schema database backed Web App or API then yeah, sure, both Rails & Django are clearly still the most mature and fully featured frameworks. Yes, there's plenty of other interesting things happening, and yes Django is
114.
by tomchristie 13y ago
Absolutely this, yes. Projects need an initial strong voice to set the voice and direction. Once a community forms around that and starts reinforcing that identity the leaders can move into more of a passive maintainer role.
115.
by tomchristie 13y ago
If you believe you've found a security issue in Django REST framework I suggest raising emailing the security contact as listed here: http://django-rest-framework.org/#security Having said that, it's worth pointin
116.
by tomchristie 13y ago
> How much of Men's magazines column inches are given to tech? As a rule, shit loads.
117.
by tomchristie 13y ago
If anyone's interested in pushing that forward a good place to start would be this thread on the django-dev mailing list: https://groups.google.com/forum/#!searchin/django-developers...
118.
by tomchristie 13y ago
Worth noting that it's an explicit aim of vanilla views to exactly replicate the functionality of Django's GCBVs. For the docs: "If you believe you've found some behaviour in Django's generic class-based views tha
119.
by tomchristie 13y ago
No problem :)
120.
by tomchristie 13y ago
> We should fork django-extra-views and see what we can come up with. Yup, that'd be interesting. Hopefully you've seen my comment to that effect here: http://django-vanilla-views.org/topics/django-extra-v

More ›