#20653: Rename new checksetup manage command
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Core (Management | Resolution:
commands) | Triage Stage: Accepted
Severity: Release blocker | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Description changed by russellm:
Old description:
> In commit
> [https://github.com/django/django/commit/91f317c76d503b4bcae5a26c230425944dbf4ea8
> 91f317c7] Daniel committed a new management command called "checksetup"
> to perform warning-level checks for problems that may occur on upgrading
> between versions.
>
> There is some overlap here between this new feature, and the scope of the
> 2013 GSoC project to refactor the "validate" command. One of the aims of
> this project is to reduce the naming collisions around "validate" -- it
> could refer to "form validation", "model validation" or "field
> validation", depending on how it's used.
>
> This GSoC project will also involve the introduction of a
>
> Before 1.6 is finalized, we should rename checksetup so it can be used as
> a generic command for all checks, rather than just the single-purpose
> check it's currently performing.
New description:
In commit
[https://github.com/django/django/commit/91f317c76d503b4bcae5a26c230425944dbf4ea8
91f317c7] Daniel committed a new management command called "checksetup" to
perform warning-level checks for problems that may occur on upgrading
between versions.
There is some overlap here between this new feature, and the scope of the
2013 GSoC project to refactor the "validate" command. One of the aims of
this project is to reduce the naming collisions around "validate" -- it
could refer to "form validation", "model validation" or "field
validation", depending on how it's used.
This GSoC project will also involve the introduction of a new management
command as part of reducing this naming collision; one of the candidate
names was "check"
Before 1.6 is finalized, we should rename checksetup so it can be used as
a generic command for all checks, rather than just the single-purpose
check it's currently performing.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/20653#comment:2>
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/066.5aedf6ec78bc9b9b591931ea077d9207%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
