Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  closed
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Normal
 Resolution:  wontfix|   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by russellm):

 As a side note, the proposed behavior would actually break a bunch of
 really useful features, including the way that static media is served by
 the runserver.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  closed
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Normal
 Resolution:  wontfix|   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by anonymous):

 * status:  reopened => closed
 * resolution:   => wontfix


Comment:

 Actually, we've never promised anything about the order of evens in
 `INSTALLED_APPS` - the documentation's careful to indicate that the order
 ought to be considered an implementation detail, not an API. Given that,
 I'm going to mark this wontfix.

 However, there's a very real need here for a consistant, accurate,
 bulletproof way to override management commands. A new ticket regarding
 that would be most welcome (especially if it has good ideas!)

 Thanks!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  closed
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Normal
 Resolution:  wontfix|   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jacob):

 Oops, that ^^^ was me. Sorry.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  reopened
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by vanschelven):

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


Comment:

 Bewgh... the spam also marked this as "fixed"

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  reopened
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * needs_docs:  1 => 0
 * needs_better_patch:  1 => 0
 * ui_ux:  1 => 0
 * has_patch:  1 => 0
 * milestone:  1.4 =>


Comment:

 Revert spam :(

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  reopened
   Type:  Bug|  Component:  Core (Management
  Milestone:  1.4|  commands)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |Needs tests:  0
Needs documentation:  1  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-

Comment (by anonymous):

 sdfsfdfgdfg gfgfdg hghgfh hgfhgf

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  reopened
   Type:  Bug|  Component:  Core (Management
  Milestone:  1.4|  commands)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |Needs tests:  0
Needs documentation:  1  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-
Changes (by anonymous):

 * status:  closed => reopened
 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * ui_ux:  0 => 1
 * resolution:  fixed =>


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
-+-
   Reporter: |  Owner:  nobody
  vanschelven| Status:  closed
   Type:  Bug|  Component:  Core (Management
  Milestone:  1.4|  commands)
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by anonymous):

 * status:  new => closed
 * needs_better_patch:   => 0
 * milestone:   => 1.4
 * component:  Uncategorized => Core (Management commands)
 * needs_tests:   => 0
 * type:  Uncategorized => Bug
 * needs_docs:   => 0
 * resolution:   => fixed


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #16599: Management commands are collected in the wrong order

[Django]

#16599: Management commands are collected in the wrong order
---+---
 Reporter:  vanschelven|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Uncategorized
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+---
 When multiple management commands of the same name exist, the ones found
 in apps higher in the INSTALLED_APPS should get precedence; right now,
 it's reversed.

 This is completely analogous to the problem described (and fixed) in
 https://code.djangoproject.com/ticket/14924
 One could basically read that ticket and replace "translations" by
 "management commands".

 In this case, the relevant update statement may be found below:
 
https://code.djangoproject.com/browser/django/trunk/django/core/management/__init__.py?rev=16222#L117

 I'm awfully sorry, don't have the time now to submit a patch. My thoughts
 would be: either run through the apps in reversed direction, or don't work
 with an update statement, but rather only add values to the dict if
 they're not present yet.
 The previous, analogous solution is indeed based on 'reversed' and may be
 found here:
 https://code.djangoproject.com/changeset/15441#file2

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.