On Feb 28, 4:39 pm, Ramiro Morales <cra...@gmail.com> wrote:
> I suspect the reason is a cleanup performed during the 1.4 development cycle > in handling of options passed to management commands that focused in the > options passed via the command line. > > You are seeing this because presumably you are using the command y calling it > from Python code. A valid use case. Perhaps an addition to the release notes > would be helpful. > > Now, the mentioned cleanup was performed well before the 1.4 alpha (Dec 27 > 2011): 1 Oct 23 2011 so I don't understand how you are seeing the change in > behavior between alpha1 and beta1. > > -- > Ramiro Morales Sorry, my fault, seems it was version 1.3 without this bug, but 1.4a also has it. Thanks for your reply. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
