4,122 karma · joined December 8, 2008
... and y'know, Python 3 should be on your radar, if not necessarily what you use right now. It's better than Python 2 in every way (except for adoption, and that's changing). 3.3 in particular has a ton of really great new stuff (futures! working namespace packages! yield from!) that you'll wonder how you lived without.
Django 1.5 has "full" Python 3 support, at least from a technical level. It's done, works, is well-tested. I'm planning on putting a Django 1.5 / Python 3.3 site into production later this year. So in that sense it's "done" now.
However, we sorta have to hedge our bets in terms of what we recommend others do.
We have a pretty serious backwards-compatibility promise, and we're not 100% certainly we've nailed down all the Python 3 APIs perfectly. There's a small (but non-zero) chance something might need to change between 1.5 and 1.6; we want the ability to make that change backwards-incompatible (for Python 3 users) if possible.
Similarly, there's a small (but again non-zero) chance that there's a serious bug or three in the Python 3 support. We don't want people getting bitten.
Finally, much of the "good stuff" in Django-land is actually in third-party apps, many of which don't yet support Python 3. This puts a pretty big obstacle in the way of a Django/Py3 site -- most real-world sites use a ton of third-party stuff. So to use Django on Py3 right now you'll need to make a bunch of "should I DIY this component or port it to py3 and submit a patch?" decisions.
In the case of the site I mentioned up top these are tradeoffs I'm willing to make. I know Django well enough to not be worried about potential bugs or backwards-incompatibilities, and I have the luxury on this project of getting to work on py3 patches as part of the deal.
Most people won't be so lucky, though, so we expect the majority of Django users to wait until 1.6 to start seriously using Py3.
We don't have a firm timeline yet. I'm guessing something like 6-9 months for 1.6, but that depends on a lot of different things. It could be longer, as much as a year, or possibly even as short as 3-4 months. We'll see :)
[BTW, you might want to be careful with the celebrity endorsement. I can't think of a celebrity I find more noxious than Kutcher, so attaching his name to Fab makes me much much less likely to buy anything from you again. Especially when you're forcing that association into my inbox. Blech.]
I really hope this is a mistake and not part of this third "pivot".
I don't know enough about Denmark to know whether gender discrimination persists in technical fields, but my guess is that women make up far less than half of the technical workforce (that's the case for most of Europe [2]).
[1] http://economix.blogs.nytimes.com/2010/03/09/the-gender-wage... [2] http://dl.acm.org/citation.cfm?doid=543812.543839
* You don't have a right to attend a private event. The organizers of any event - a conference, a concert, whatever - have the right to ask you to leave at any point for any reason. You are, in fact, more protected with a code of conduct in place because it articulates the process instead of leaving it up to the whims of the organizers.
* You don't have any right to due process or "legal protection"; the conference organizers aren't the police! They're not deciding what's "truth" or not; they're deciding whather to allow you to stay at an event they're responsible for.
* If you're talking about PyCon, it's hardly "a few local programmers". PyCon is a conference with a large staff, a budget of over a million dollars, and an established NPO (the PSF) behind it.
* If you can't trust the organizers of an event, then why the heck are you attending?
* People don't just randomly make up harassment. In reality, harassment is vastly underreported because of the way victims of harassment are routinely ignored, shamed, and blamed.
* Wanna know a really good way to not be accused of harassment? Don't harass anyone! If you find not being a harasser so hard, then yeah you probably shouldn't go to the event.
Which country is that?
I'm curious: where did you read/see that?
Yes, McCabe is a real thing. I haven't really found it that useful myself -- I'm not sure that you can adequately measure something fuzzy like "complexity" through static control flow analysis -- but sure, I'm willing to accept that it could be useful in certain circumstances.
What I am saying is that this guy is cherry-picking a specific metric (out of many that he could choose) that makes his tool looks good. I could just as easily come up with a metric that sorts Django to the top of an arbitrary list. That wouldn't be useful, either.
Yes, I'm a maintainer of Django, so I'm biased too. But look: there's a good argument to be made that parts of (even of all of) Django is too complex. This, however, is not that argument; this is just a made-up metric.
ETA: I misspoke above: McCabe isn't made up. I meant to write that this was a cherry-picked metric. Leaving the above as is because people have already replied to it.
Yes, this is a good idea in theory (it's an offshoot of the idea of avoiding using any data that's provided by the browser.) But in practice, it breaks down any time you need to generate a full URL into the site, i.e.:
* Callback URLs for schemes like OAuth, webhooks, IPN, etc. * Transaction emails with links back to the site ("this week on example.com", "joe just mentioned you..." password resets, etc.) * Links in Atom, RSS feeds, etc.
In each case, Django could require that hosts be hardcoded (perhaps in settings) instead of consulting requests, but that would make each of those things harder to use.
... I'm not really trying to have an argument here; I see your point completely and I think I probably agree, personally. But I am trying to point out that security and usability are often at odds, and that there isn't as much a "right answer" as there is a calibration between those two needs. Drawing the line in the right place is hard.
On the other hand, you're completely right that the "you gotta get your upstream server configured correctly" advice is handwavy at best.
Seems like this is always the case, this tension between security and usability...
If you've got bright ideas, I'd love to hear 'em. Maybe join us on django-dev (http://groups.google.com/group/django-developers) if you do?
No, it's not. As the release notes say, "Some attacks against this are beyond Django's ability to control, and require the web server to be properly configured"; see https://docs.djangoproject.com/en/1.4/topics/security/#host-... for details.
[So please upgrade!]
1. Yes, we're (painfully) aware that restoring users' trust is going to be a big deal. There's obviously no way I can prove the future, so all I can say is that we're in this for the long haul. Grove fits in perfectly with our business, is a product that we fundamentally believe in, and so it's not going anywhere. We're not going to sell it, or shut it down, or "pivot" into a different business. I hope I have a good enough reputation that you can take me at my word, but whatever: our actions over the coming months and years will prove this.
2. We're not re-branding; that feels dishonest (plus, I love the brand.) I'm confidant that we can restore whatever trust we've lost.
3. Oh hells yes, I want an awesome mobile site/app, too. Realistically it's a bit down the list after some of the backend stuff we need to hammer our first. But I want one, bad, so it'll happen as soon as we can!
Thanks again for the feedback, it's really helpful. If you've got anything else you'd like to tell me/us -- or if there's anything more I can do to get you back as a user -- please drop me a line (jacob at jacobian.org).
I know migrating (again!) is a pain, but if you ever want to give Grove another try, please get in touch (jacob at jacobian.org) and let me know what we'd need to do to get you back.