Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  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|
-+-

Comment (by Tim Graham ):

 In [changeset:"b30a872973b6903e52d93532175d60d3bf68f888"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b30a872973b6903e52d93532175d60d3bf68f888"
 [1.6.x] Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

 Thanks CollinAnderson for the report.

 Backport of a7d97a6778 from master
 }}}

-- 
Ticket URL: 
Django 
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.41ac845cd18bd7e6fea66e91f7b7285c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  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|
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a7d97a6778ca528199920901ed2f66e289ee5a44"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a7d97a6778ca528199920901ed2f66e289ee5a44"
 Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

 Thanks CollinAnderson for the report.
 }}}

-- 
Ticket URL: 
Django 
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.41de4b9bd85179247201ade59dc30c99%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#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|
-+-
Changes (by CollinAnderson):

 * status:  closed => new
 * resolution:  fixed =>


Comment:

 checksetup is still in the django-admin docs
 https://github.com/django/django/blob/master/docs/ref/django-admin.txt#L92

 https://github.com/django/django/pull/1353

 (i figure this is small enough to not warrant a new ticket number.)

-- 
Ticket URL: 
Django 
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.9c87ba6e3af7df486920893c8f0f2cf5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  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|
-+-
Changes (by russellm):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Trac triggers seem to be busted; this was committed in
 
[https://github.com/django/django/commit/0346563939396fb89dec8df31f82eaefaaeb8616
 03465639]

-- 
Ticket URL: 
Django 
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.7c29ccbc3f1de4818ba2ea6f1d0874e4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#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|
-+-

Comment (by russellm):

 Consensus on mailing list seems to be that "check" is the best name; I've
 got a commit for this that will land shortly.

-- 
Ticket URL: 
Django 
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.63edac54a581e5ea5a1efde03e9a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#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|
-+-

Comment (by russellm):

 [https://groups.google.com/d/msg/django-
 developers/IBLzFNua81k/RDpoE6jvRUcJ Mailing list discussion here]

-- 
Ticket URL: 
Django 
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.7815ef07b9ef579fb71518ce08e861d2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#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: 
Django 
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.

[Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
   Reporter:  russellm   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Core   |   Keywords:
  (Management commands)  |  Has patch:  0
   Severity:  Release|Needs tests:  0
  blocker|  Easy pickings:  0
   Triage Stage:  Accepted   |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 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.

-- 
Ticket URL: 
Django 
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/051.b9a61e203b8e95c8fe18decb0747b1ff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.