HNHacker News
TopNewBestAskShowJobs

jacobian

4,122 karma · joined December 8, 2008

http://jacobian.org/
submissionscomments
jacobian··on Django Code of Conduct - feedback wanted
Sorry if it seems sudden or ill-timed. The truth is that we've been working on this for quite some time (long enough I've forgotten when exactly we started). Like most things in open source, we worked on it when we found time, and released it when it was ready.
jacobian··on Django Code of Conduct - feedback wanted
Thanks a good suggestion; thanks. Can you repeat it via the feedback form (https://www.djangoproject.com/conduct/#feedback) so that we don't lose track of it?
jacobian··on Django Code of Conduct - feedback wanted
The Ada template is something different, being mostly designed for in-person events. There's more on that here: https://www.djangoproject.com/conduct/#dsf-events. If you've got further questions, can you leave 'em via the feedback form? Otherwise we might miss 'em.
jacobian··on Django Code of Conduct - feedback wanted
Hi folks - If you've got feedback that you'd like us to take into account, can you please send it via the form (https://www.djangoproject.com/conduct/#feedback)? I have a shitty memory, and if you just leave suggestions here I'll probably forget 'em. Thanks!
jacobian··on Django Code of Conduct - feedback wanted
Nope. We've been working on this for... quite a few months, actually.
jacobian··on Django Code of Conduct - feedback wanted
I'm sorry you feel that way; that wasn't our intent. If you've got ideas about how we might improve it, please let us know: https://www.djangoproject.com/conduct/#feedback.
jacobian··on Donglegate: Why the Tech Community Hates Feminists
> I think the type of comments you mentioned are not only relatively rare, but they are quickly downvoted when they occur.

Well, we see a very different subset of comments, apparently.

Look at the top comments in this very thread, for example...

jacobian··on Donglegate: Why the Tech Community Hates Feminists
Go read any thread here touching on sexism, feminism, or gender equality. You get all the standard anti-feminist arguments ("it's not really a problem"; "men are oppressed too"; "she should have just asked nicely"; "my wife doesn't think that's sexist"; "it's just a joke"; etc. etc. etc.) I'm not sure I'd lump HN in with the MRA jerks wholesale, but in all HN reeks of privilege. There are several things HN does very well; gender equality really isn't one of them.
jacobian··on How To Get Banned From PyCon
FYI, here's PyCon's official statement on this incident: http://pycon.blogspot.com/2013/03/pycons-response-to-inaprop....

I think it may answer some of the questions people have here; if you have additional questions please email me (jacob@jacobian.org) and I'll do my best to answer 'em.

jacobian··on Goodbye, Malcolm
Out of respect for Malcolm's friends and family we're waiting to share more details until we know what they're comfortable sharing.
jacobian··on Python.org Redesign Preview
These are awesome, thank you!
jacobian··on Python.org Redesign Preview
The code's not open source yet, but it will be. The idea is we'll deliver what we've promised to the PSF, then launch the site for real (i.e. replace python.org) and open source the code at the same time. We want to make this into a community-maintained thing, but first we got some real work to do :)
jacobian··on Python.org Redesign Preview
Do you think you can clarify? Most people seem to think that Python's docs are quite good — it's one of the things that originally brought me to Python, along with many others. If you can explain how they let you down perhaps we can do something to fix it?
jacobian··on Python.org Redesign Preview
Thanks for the feedback, good stuff.

As for contributing: we'll be releasing the code when we launch the site for real (i.e. actually replace python.org), and we'll certainly be taking pull requests. I'll also have some contributor guidlines written up by that point.

We've got some serious work to do first, though :)

jacobian··on Python.org Redesign Preview
Thanks for the feedback, good stuff.

BTW, please do try the nav on mobile devices, especially tablets. They work there, too, and I think our designers did something especially slick :)

jacobian··on Python.org Redesign Preview
Brilliant.
jacobian··on Python.org Redesign Preview
Yeah, that example is a placeholder; we plan on replacing it with something awesome. Thanks!
jacobian··on Load Balancing without Load Balancers
What, exactly, does the picture of a woman in a swimsuit have to do with load balancing?
jacobian··on Django 1.5 released
Thanks, that's a good point. Hopefully we can do something about that in 1.6.
jacobian··on Django 1.5 released
Of your list:

* South doesn't have Py3 support in core, but there's a fork that does and seems to work perfectly: https://bitbucket.org/aaugustin/south-python3

* lxml as of v3 seems to have py3 support (I haven't tried it, but looks like it does).

* simplejson is now in the standard library as "json", so yes there.

* requests works, since v0.10 (about a year ago).

* django-compressor is not ported; however, django-pipeline does run on Python 3 and is basically -compressor's successor. It works great.

* gunicorn works on py3 (as does uwsgi and mod_wsgi, btw.)

* jinja2 hasn't been ported yet.

* twisted is actively being ported right now, and has gotten to the point of "kinda working". You can follow along at http://twistedmatrix.com/trac/milestone/Python-3.x and http://twistedmatrix.com/trac/wiki/Plan/Python3.

* txAMQP probably can't get ported until twisted does.

* django-rest-framework has Python 3 support, I think it's fairly recent, but it works well.

This list is about typical of what I've found doing Django/Py3 work: many things are ported, a bunch more have good alternatives, and a few things are still missing.

jacobian··on Django 1.5 released
FWIW, that "experimental" label doesn't quite mean that 1.5 isn't ready for prime-time; it's more about setting community expectations. Please see my reply elsewhere in this thread (https://news.ycombinator.com/item?id=5289006) for more details.

ETA: That said, the advice to stick to Py2 right now is probably good. There's still some key missing 3rd party packages, so you'll generally be happier as a Py2 user right now.

jacobian··on Django 1.5 released
FYI, the "experimental" thing is a community thing, not really a technical judgement. Since this is our first Python 3 release, we want to have some space to make changes between 1.5 and 1.6 that we otherwise would avoid because of our strong backwards compatibility promise. The "experimental" label is about giving ourselves that room and not surprising users if there do have to be changes in the way Py3 support works between 1.5 and 1.6.

Technically, however, it's pretty rock-solid. I'll be launching a site built on Py3/1.5 is about two weeks, and aside from constantly forgetting to `print(...)` instead of `print ...` it's been surprisingly smooth sailing.

jacobian··on Django 1.5 released
I'd love to know more about the "jaw-dropping nastiness" so we can fix it in 1.6. Can you elaborate, please?

[I'm a Django committer, FWIW.]

jacobian··on Security releases issued
Would you maybe consider making a distinction between security releases and regular run-of-the-mill update releases?

I see a real value in a service to let me know that there's a new version of one of the dozens of things I depend on. But like I said, it seems janky to rely on a for-pay service to find out about security vulnerabilities. So what about making the security notification free to all users, with the non-security update notifications a for-pay addon? Seems like a good way to strike a balance between developing a self-sustaining business and helping out a community.

jacobian··on Security releases issued
Yes: Django only uses XML in one very limited place, the serialization parsing framework, which isn't exposed publicly in any way. It's used for data backup/restore as well as for test fixtures, but that's it. Further, the same framework also supports JSON, and it's extremely rare to find a Python developer who's going to chose XML over JSON. So in terms of Django itself the attack surface is extremely small.

That said, if you're parsing XML in your own code you should be looking at defusedxml, also announced today: http://blog.python.org/2013/02/announcing-defusedxml-fixes-f.... So maybe we should make a bigger point about that? If you've got suggested edits to the announcement let me know, happy to incorporate 'em.

jacobian··on Ask HN: State of Django vs. Rails?
Obviously I'm totally biased and you shouldn't listen to me.

But if you were to listen to me, I'd probably be saying something about how they're basically equivalent these days. Both are pretty productive, have clean readable code, are well-documented, have active communities, a wide array of plugins and tools, and are fairly easy to use.

If you were to get even crazier and try to get some advice on which you should use, I'd probably tell you that Rails is best if you already know Ruby; Django if you already know Python. If you don't know either, take a week or two and build a site with both and see what sticks. Either way you'll be pretty happy.

But you shouldn't listen to me because I'm heinously, terribly biased, so you probably didn't hear me say any of that. Just as well.

jacobian··on Security releases issued
Yup, it's not the first time either -- we've coordinated with them in the past when fixing bugs that affect both frameworks (https://www.djangoproject.com/weblog/2011/feb/08/security/).
jacobian··on Security releases issued
That's 100% completely wrong. We've worked with Rails' security team in the past to coordinate releases fixing similar issues, and they've helped us out with discovering and analyzing issues of our own.

They're a great group of people and I've got nothing but good things to say about our work together.

Yet another reason why open source is fantastic: friendly competition can actually be friendly. It rocks.

jacobian··on Security releases issued
We don't just announce this stuff on HN; there's a whole lot more:

* Post security release announcements to our blog.

* Post announcements to django-announce, a very low-traffic mailing list specifically for security announcements.

* Post announcements to django-users, a mailing list with over 20,000 subscribers from all over the Django community.

* Post announcements to django-developers, where most of the people who hack on Django hang out.

* Publicize these releases on Twitter, Reddit, HN, etc.

Further, we work with people who re-distribute Django (e.g. as part of RHEL/Fedora/Ubuntu/etc.) and people who use Django in high-risk areas to get them early access to security notifications [1].

So yeah, we make a lot of noise about security issues.

BundleScout looks nice, but it kinda sucks that you'd make people pay to hear about security issues. We're going to continue to do our best to make sure people find out about them quickly and for free.

[1] https://docs.djangoproject.com/en/dev/internals/security/#re...

jacobian··on Security releases issued
These aren't "drop everything, take the site down, upgrade now" issues, so yeah we'd like to save the tone for that sort of thing.

... but seriously, please do upgrade as soon as possible! There's really no such thing as a "minor" security issue when it's 2am and you're being woken 'cause the site's down.

← PreviousPage 3 of 10Next →