Re: django.core.management.dump_data gone into management.commands - but how to address it?

On 8/29/07, Ulf Kronman <ulf.kronmanbredband.net> wrote:
> Is there any documentation on this change around yet?

As always, backwards-incompatible changes appear here:

http://code.django
project.com/wiki/BackwardsIncompatibleChanges#Changestomanag
ement.pycommands

-- 
"Bureaucrat Conrad, you are technically correct -- the
best kind of correct."

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

> > Is there any documentation on this change around
yet?
> As always, backwards-incompatible changes appear here:
> http://code.djangoproject.com/wiki/Backw
ardsIncompatibleChanges#Chang...

Thanks again.

I also notice that the command names have changed from
dump_data and
load_data to dumpdata and loaddata, respectively. I guess
that this
means that in the future, we should always presume that
management
commands are addressed with the lowercased Python filename
from the
directory management/commands. Right?

// Ulf


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---