Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.9 Released

djangoproject.com

Post reply on HN
Print view View original

51–60 of 91 posts

Re: Django 1.9 Released

#51

Post by japhyr »

jsmeaton wrote: post #11

This might be a good time to mention that Django is always trying to raise funds: https://www.djangoproject.com/fundraising/ The really quick turn around on tickets and pull requests is largely thanks to the Django Fellow, who is paid to manage the community. The last two or three releases have been on time because of the Fellow. The Fellow is funded via Django Software Foundation fundraising activities. If your comp…

I just started watching videos from this year's PyCon Australia [0]. Russell Keith-Magee, a core Django developer, gave an interesting talk called "Money, Money, Money - Writing software in a rich (wo)man's world" [1].

I love open source software, and I want to see more high-quality open source. I want to see established projects like Django continue to thrive. If you're curious about how funding impacts the quality of open source projects, you might want to check out Russell's talk.

[0] - https://www.youtube.com/playlist?list=PLs4CJRBY5F1KMMpoEWMuB...

[1] - https://www.youtube.com/watch?v=mY8B2lXIu6g&list=PLs4CJRBY5F...

Re: Django 1.9 Released

#52

Post by japhyr »

jsmeaton wrote: post #43
jkarneges wrote: post #33

Before anyone says something about Django not being hip enough for realtime stuff, just know that you can layer Pushpin ( http://pushpin.org ) in front of it. This may sound like a bandage but it's actually good design, regardless of programming language. Disclaimer: author.

Andrew Godwin (the author of django migrations and south before that) is working on something he calls Django Channels http://channels.readthedocs.org/en/latest/ . The aim is to bring it into core (possibly for 1.10), which will allow real time features. The traditional request/response cycle will then just become producers and consumers of a "request" channel.

This is great to hear. I learn a lot from watching how the Django team brings critical third-party projects into the core of Django.

Re: Django 1.9 Released

#53

Post by jMyles »

If you are deploying a new django project, let me suggest hendrix (twisted + django) as your WSGI publisher.

hendrix makes concurrency simple, fun, and fast using Twisted, which is battle-tested and experiencing an amazing renaissance of young talent (as evidenced by the amazing vibes in the Twisted room at the PyCon sprints).

https://github.com/hendrix/hendrix

Re: Django 1.9 Released

#54

Post by japhyr »

jsmeaton wrote: post #44
pbreit wrote: post #40

Earlier quoted context omitted.

I'm shocked, frankly, at how lousy both are out-of-the-box. I just don't get why a simple CRUD app (which many/most apps are) has to be so difficult. I had trouble figuring out how to do email login on Django and just gave up. At first, Rails seems like it's going to be a lot better. I don't care for generating files. Don't like TDD. And found the migrations very confusing (if I make a typo in a field name, I delete…

Unfortunately it looks like you hit a bit of a sore spot with regards to django auth. There isn't a good out of the box solution for email based usernames. There are patterns available, and the "swappable" user framework is there to allow email based usernames. But an email based model isn't available. I'm fairly sure there are tickets or ideas to make this happen, but we're not there yet. Django really is quick and…

Do you know how well cookiecutter-django [0] handles email logins? I've been meaning to play around with cookiecutter, but I haven't started a new project recently. Cookiecutter uses django-allauth [1], which seems to offer email login methods, from what I see in a cursory look at the docs [2].

[0] - https://github.com/pydanny/cookiecutter-django

[1] - https://github.com/pennersr/django-allauth

[2] - http://django-allauth.readthedocs.org/en/latest/configuratio...

Re: Django 1.9 Released

#55

Post by jsmeaton »

jMyles wrote: post #53

If you are deploying a new django project, let me suggest hendrix (twisted + django) as your WSGI publisher. hendrix makes concurrency simple, fun, and fast using Twisted, which is battle-tested and experiencing an amazing renaissance of young talent (as evidenced by the amazing vibes in the Twisted room at the PyCon sprints). https://github.com/hendrix/hendrix

I can't say I've used twisted at all, but Amber had a fairly good talk at Django Under the Hood this year on this topic: https://opbeat.com/events/duth/#twisted-and-django

Re: Django 1.9 Released

#56

Post by Alex3917 »

jsmeaton wrote: post #44
pbreit wrote: post #40

Earlier quoted context omitted.

I'm shocked, frankly, at how lousy both are out-of-the-box. I just don't get why a simple CRUD app (which many/most apps are) has to be so difficult. I had trouble figuring out how to do email login on Django and just gave up. At first, Rails seems like it's going to be a lot better. I don't care for generating files. Don't like TDD. And found the migrations very confusing (if I make a typo in a field name, I delete…

Unfortunately it looks like you hit a bit of a sore spot with regards to django auth. There isn't a good out of the box solution for email based usernames. There are patterns available, and the "swappable" user framework is there to allow email based usernames. But an email based model isn't available. I'm fairly sure there are tickets or ideas to make this happen, but we're not there yet. Django really is quick and…

I think a bigger issue with regards to usernames and email is the fact that neither are titlecased before getting indexed. I get that there are certain legacy considerations or whatever, but it really seems like there should at least be a note in the documentation about this given the massive clusterfuck that would potentially ensue should someone not figure this out before launching.

Re: Django 1.9 Released

#57

Post by Omnipresent »

xirdstl wrote: post #16
sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

Don't forget Grails

Still waiting on REST profile for grails.

Re: Django 1.9 Released

#58

Post by jsmeaton »

Alex3917 wrote: post #56
jsmeaton wrote: post #44

Earlier quoted context omitted.

Unfortunately it looks like you hit a bit of a sore spot with regards to django auth. There isn't a good out of the box solution for email based usernames. There are patterns available, and the "swappable" user framework is there to allow email based usernames. But an email based model isn't available. I'm fairly sure there are tickets or ideas to make this happen, but we're not there yet. Django really is quick and…

I think a bigger issue with regards to usernames and email is the fact that neither are titlecased before getting indexed. I get that there are certain legacy considerations or whatever, but it really seems like there should at least be a note in the documentation about this given the massive clusterfuck that would potentially ensue should someone not figure this out before launching.

Do you mean that usernames/emails aren't normalised to a single case to prevent "duplicates" of "jarshwah" and "Jarshwah"? If so, this was recently brought up on the mailing list: https://groups.google.com/forum/#!topic/django-developers/SW...

I agree this should probably have a solution or at least documentation to be wary of.

Re: Django 1.9 Released

#59

Post by japhyr »

I just got around to skimming the release notes, and I'm curious about running tests in parallel. I'm looking forward to upgrading, and seeing if this has a meaningful impact on my tests. I don't have a large number of tests yet; my project runs its full test suite in ~10 seconds at the moment. But I'm well aware this should grow significantly as my project matures.

Does anyone have any sense yet of how this affects the speed of the test suite in your real-world projects?

https://docs.djangoproject.com/en/1.9/releases/1.9/#running-...

Re: Django 1.9 Released

#60

Post by Alex3917 »

jsmeaton wrote: post #58
Alex3917 wrote: post #56

Earlier quoted context omitted.

I think a bigger issue with regards to usernames and email is the fact that neither are titlecased before getting indexed. I get that there are certain legacy considerations or whatever, but it really seems like there should at least be a note in the documentation about this given the massive clusterfuck that would potentially ensue should someone not figure this out before launching.

Do you mean that usernames/emails aren't normalised to a single case to prevent "duplicates" of "jarshwah" and "Jarshwah"? If so, this was recently brought up on the mailing list: https://groups.google.com/forum/#!topic/django-developers/SW... I agree this should probably have a solution or at least documentation to be wary of.

Yeah, I actually hadn't seen that, but I know there are also longstanding tickets for this. I actually don't like the solutions in those threads, I think better to just add an extra field to the models, so have something like 'db_email' and 'display_email'. I realize you can do this with a functional index or whatever, but I think that's actually kind of hacky given the lack of ORM support for functional indexes.

My big issue with the current state though is that if you're relying on usernames or email addresses being unique then you're potentially opening yourself up to all sorts of security issues without realizing it.

Post reply on HN