3 ms·
> We try to keep Django's dependencies down to the Python standard library Any good reasons for this?
by houseabsolute 17y ago
> We try to keep Django's dependencies down to the Python standard library
Any good reasons for this?
- simonw 17y agoPersonal opinion: It's probably one of the reasons we're the most popular Python web framework, especially amongst people with no prior Python experience. We may change that policy in the future (we've discussed it) but we're not going to change it just so the signing feature can get in to Django 1.2 - and I'd really like to get signing in to 1.2.
- houseabsolute 17y agoIt will be interesting to see if anyone has their identity stolen as an indirect consequence of this decision.
- deleted 17y ago[deleted]
- tptacek 17y agoNobody is going to have their identity stolen because of this feature, but it would be nice if they stopped implementing any more crypto. Arguing against signed cookies is tilting at windmills, but that doesn't mean marketing crypto features is a smart move.
- ubernostrum 17y agoAdding to what Simon said, dependencies in Python are an absolute mess, with no truly reliable mechanism other than saying "here's a list of what you'll need, go install it all manually". So every additional dependency is a major burden in terms of packaging, documentation, learning curve for newbies, etc. and we try to avoid inflicting that unless it's absolutely necessary. (though personally I think I'd prefer to outsource crypto to, you know, people who actually know how to do it)