4 ms·
A) The kind of complexity you're referring to is different from what this blog post is talking about. (Specifically cyclomatic complexity.) B) Django doesn't h
by ericflo 14y ago
A) The kind of complexity you're referring to is different from what this blog post is talking about. (Specifically cyclomatic complexity.)
B) Django doesn't have its own cheeseshop. Django developers use PyPI and pip just like everyone else. (Maybe you're thinking of Crate.io, which is a PyPI mirror that happens to use Django in its implementation.)
- chewxy 14y agoOh. Thanks for setting me straight on the cheeseshop (I actually thinking that since it has its own package management system, it would have its own cheeseshop) Sorry. As for complexity, I still think it's excessive. It's good to know the internals of a module/package/whatever, and django is really really complex, of which cyclomatic complexity quantifies I believe. I mean, if you have code that branches off everywhere, it'd be hard to follow the logic when inspecting the internals.
- jacobian 14y agoSo Django doesn't have its own package management system, either. I'm curious: where did you read/see that?
- shabble 14y agoMaybe the 'django [reusable] app' terminology? One of the first few pages in the tutorial includes: "Django apps are "pluggable": You can use an app in multiple projects, and you can distribute apps, because they don't have to be tied to a given Django installation." and I guess it might be possible to mistake 'manage.py startapp ...' as some sort of internal packaging thing if you don't look too deeply.
- chewxy 14y agoYah. Obviously I was mistaken. But your points exactly
- chewxy 14y agoHoly ... jacobian replied me. To answer your question: I am an idiot and I didn't know much about Django. I did once find djangopackages or something like that and simply jumped to the conclusion. Big and Unwieldly is the brand perception I had.