On 29 Jul 2006, at 13:18, GinTon wrote:
And I'll have to change the name of 'localization' used in my project to something as country or countries.
Well if I can make this worth of inclusion in django core naming will not be a problem because no new namespace will be introduced, just django.utils.localization along with django.utils.translation.
Until then it will probably be under nesh.* namespace like other stuff I published.
I'm also thinking to separate currency handling into another app because it will need some sort of exchange rate database and currency conversion handling functionality which will not be needed for most of the projects.
Hmmm, we definitely need some sort of naming guidelines for django add-on applications.
I hope that some of the core developers (and Hugo) are watching this thread. I'll definitely like to hear their opinion on this.
-- Nebojša Đorđević - nesh Studio Quattro - Niš - Serbia http://studioquattro.biz/http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/ | http://trac.studioquattro.biz/djangoutils/
Registered Linux User 282159 [http://counter.li.org]
PGP.sig
Description: This is a digitally signed message part
