This seems like the most reasonable approach. FWIW, why not name it just django-localflavor?
Cheers, AT On Tue, Oct 16, 2012 at 7:00 AM, Łukasz Rekucki <lreku...@gmail.com> wrote: > Maybe we need something like django-localflavour-commons, which would > include the test harness, packaging logic (then in setup.py you can > just import it from there), etc. My first idea was to make it a > submodule, but that would still require making a commit to all repos > whenever we update the commons (althought, still simpler then applying > the same patch everywhere). We could instead put it on PyPI and make > all other packages always require it's latetest version. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
