Yeah, it's amazing that we have GeoDjango included as I'm using it right now.
However I can fall back to geopy and still getaway with rough acceptable estimates with limited scope and capability which I'm fine with. (In my use case) If I had to choose between GeoDjango and South as a core package, I'd go with South for sure. GeoDjango might be for the 10% while South can be for the 90%. Admin is a must for the beginners. And if we want to attract more people to use Django, then admin is the tool right out of the box. I wish there was a way to have the core developers in charge of the core packages, the vision and the direction. They would also be in charge of blessing the contrib packages that are not a MUST. (contrib.auth is a must) Then we could have a secondary team that takes care of the packages that fall In the same category as GeoDjango. It would be a nice divide and conquer strategy and both teams can help maintaining the "sync" state. pip install Django pip install Django-contrib Just a wild thought. :) Val Sent from my mobile device. On 2013-02-06, at 2:33 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > The only historically-accurate answer is: "because it seemed like a > good idea at the time." > > Remember, this was 2008. So one problem was that Django's DB APIs > weren't very polished, so GeoDjango had to do a bunch of trickery. > Bringing it into core gave a good way towards pushing that flexibility > down into the DB layer. Further, Python packaging was in a sorry > state; keeping a version of GeoDjango installed and in sync with a > version of Django wasn't exactly easy (the tight coupling between > GeoDjango and Django means that you really need to versions to match > up.) Finally, GeoDjango was an incredibly powerful addition to Django, > something that wasn't available in any other web framework. Having it > available out of the box really set us ahead of all other tools, at > least in the GIS space. > > How much of this is still true is left as an exercise to the reader. > > Jacob > > PS: I'm not exactly sure what you mean by the admin being a candidate > for removal. I don't think anyone's suggesting that, at least not > seriously. > > On Wed, Feb 6, 2013 at 1:20 PM, Maxime Haineault <hainea...@gmail.com> wrote: >> I've seen lot of talk about removing the admin and many other contribs from >> core. >> >> For some I think it make sense, for others like the admin I'm not so sure. >> >> However, I have not seen any talk about removing GeoDjango and I'm wondering >> about the >> rational of keeping this relatively huge domain specific codebase in django. >> >> In the last five years i worked on at least 150 django projects, every >> single one of them used >> the admin and only one required GeoDjango. >> >> I'm not advocating that it should be removed, but I can't help but wonder >> why the admin would >> be a good candidate for removal and not GeoDjango. >> >> Regards >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
