#23456: requires_system_checks and requires_model_validation
-------------------------------+--------------------------------------
     Reporter:  pablofm        |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  closed
    Component:  Uncategorized  |                  Version:  1.7
     Severity:  Normal         |               Resolution:  worksforme
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => worksforme


Old description:

> I've uploaded from django 1.6 to django 1.7 and from python 3.2.3 to
> python 3.4.1.
>
> Suddenly when I try to run the makemessages command to catch the
> translating messages I find this error:
>
> django.core.exceptions.ImproperlyConfigured: Command Command defines both
> "requires_model_validation" and "requires_system_checks", which is
> illegal. Use only "requires_system_checks".
>

>
> I've uploaded from django 1.6 to django 1.7 and from python 3.2.3 to
> python 3.4.1.
>
> Suddenly when I try to run the makemessages command to catch the
> translating messages I find this error:
>
> django.core.exceptions.ImproperlyConfigured: Command Command defines both
> "requires_model_validation" and "requires_system_checks", which is
> illegal. Use only "requires_system_checks".
>
> I've googled it and I don't find where or what I should edit. In fact
> I've never used this parameter so...
>
> Any idea?
>
> The traceback
>
> Traceback (most recent call last):
>   File "manage.py", line 10, in <module>
>     execute_from_command_line(sys.argv)
>   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 238, in fetch_command
> klass = load_command_class(app_name, subcommand)
>   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 42, in
> load_command_class
> return module.Command()
>   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
> packages/django/core/management/base.py", line 228, in __init__
> '"requires_system_checks".' % self.__class__.__name__)
> django.core.exceptions.ImproperlyConfigured: Command Command defines both
> "requires_model_validation" and "requires_system_checks", which is
> illegal. Use only "requires_system_checks".

New description:

 I've uploaded from django 1.6 to django 1.7 and from python 3.2.3 to
 python 3.4.1.

 Suddenly when I try to run the makemessages command to catch the
 translating messages I find this error:

 django.core.exceptions.ImproperlyConfigured: Command Command defines both
 "requires_model_validation" and "requires_system_checks", which is
 illegal. Use only "requires_system_checks".



 I've uploaded from django 1.6 to django 1.7 and from python 3.2.3 to
 python 3.4.1.

 Suddenly when I try to run the makemessages command to catch the
 translating messages I find this error:

 django.core.exceptions.ImproperlyConfigured: Command Command defines both
 "requires_model_validation" and "requires_system_checks", which is
 illegal. Use only "requires_system_checks".

 I've googled it and I don't find where or what I should edit. In fact I've
 never used this parameter so...

 Any idea?

 The traceback
 {{{
 Traceback (most recent call last):
   File "manage.py", line 10, in <module>
     execute_from_command_line(sys.argv)
   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 238, in fetch_command
 klass = load_command_class(app_name, subcommand)
   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 42, in
 load_command_class
 return module.Command()
   File "/home/pablo/Workspaces/milao/lib/python3.4/site-
 packages/django/core/management/base.py", line 228, in __init__
 '"requires_system_checks".' % self.__class__.__name__)
 django.core.exceptions.ImproperlyConfigured: Command Command defines both
 "requires_model_validation" and "requires_system_checks", which is
 illegal. Use only "requires_system_checks".
 }}}

--

Comment:

 Maybe you are using a 3rd party package that needs to be updated?

 This ticket tracker is for bugs and new features suggestions. Please see
 TicketClosingReasons/UseSupportChannels for ways to get help. You'll
 likely need to provide more information such as a way to reproduce your
 problem in order to get help.

--
Ticket URL: <https://code.djangoproject.com/ticket/23456#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.93d6fdf6d9ddb79e02fb45d67e1477a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to