Re: [Django] #15132: The runserver command is missing --verbosity and --traceback

2011-08-14 Thread Django
#15132: The runserver command is missing --verbosity and --traceback
-+-
   Reporter:  cardonbj   |  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  django-admin.py
  Milestone: |  runserver
Version:  1.2|   Severity:  Normal
 Resolution:  wontfix|   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):

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


Comment:

 Please don't reopen tickets closed as "wontfix" by core developers. If you
 disagree with the fact that the ticket was closed, I encourage you to take
 the discussion to the django-developers mailing list. For more
 information, see the contributing guide in the documentation.

 Regarding the template for errors in AJAX queries, the problem is already
 reported in #10841, #16190 and #16227.

-- 
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] #15132: The runserver command is missing --verbosity and --traceback

2011-08-14 Thread Django
#15132: The runserver command is missing --verbosity and --traceback
-+-
   Reporter:  cardonbj   |  Owner:  nobody
   Type: | Status:  reopened
  Uncategorized  |  Component:  django-admin.py
  Milestone: |  runserver
Version:  1.2|   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 zeraien):

 * status:  closed => reopened
 * severity:   => Normal
 * cc: zeraien (added)
 * resolution:  wontfix =>
 * easy:   => 0
 * ui_ux:   => 0
 * type:   => Uncategorized


Comment:

 There is a extension called django-extensions which has a runserver_plus
 command, which runs a dev server with werkzeug debugger, but that is
 beside the point. The main point is that this runserver_plus command
 prints out a traceback of every exception thrown by the code.

 This is very useful as the OP said in developing websites that use a lot
 of AJAX or RPC requests, since having to manually read HTML when scanning
 failed requests is bullocks.

 At the very least there should be an is_ajax check that will return 500
 errors with tracebacks in plain text for any ajax request, rather than
 full HTML that it is now.

-- 
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] #15132: The runserver command is missing --verbosity and --traceback

2011-02-12 Thread Django
#15132: The runserver command is missing --verbosity and --traceback
-+--
   Reporter:  cardonbj   | Owner:  nobody
 Status:  closed | Milestone:
  Component:  django-admin.py runserver  |   Version:  1.2   
 Resolution:  wontfix|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by admackin):

 Surely it should do what it used to do in the past? According to the
 discussion here, it existed in an old SVN revision:

 http://groups.google.com/group/django-
 
users/browse_thread/thread/83d603b7aa6bc067/98bbee8c4bbfe824?lnk=gst=runserver+traceback#98bbee8c4bbfe824

 So if it could have worked once, can't it be made to work again?

 (I've got a similar problem to the OP -- this is something I would dearly
 like to reappear)

-- 
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] #15132: The runserver command is missing --verbosity and --traceback

2011-01-21 Thread Django
#15132: The runserver command is missing --verbosity and --traceback
+---
  Reporter:  cardonbj   | Owner:  nobody
Status:  closed | Milestone:
 Component:  django-admin.py runserver  |   Version:  1.2   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Marking wontfix because I'm having difficulty thinking of what either
 option would actually do.

 I can't think of a change we could make that would increase the verbosity
 of the development server -- it already reports every request that hits
 it.

 As for tracebacks -- server errors are caught and returned as 500s, but
 that's at a layer of abstraction deeper than the runserver command.

 I'm happy to entertain the general principle of "more debug is better",
 but in this case, I would need to see the specific change that is being
 proposed.

-- 
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] #15132: The runserver command is missing --verbosity and --traceback

2011-01-20 Thread Django
#15132: The runserver command is missing --verbosity and --traceback
---+
 Reporter:  cardonbj   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py runserver  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I've done some searching and don't think this is a duplicate. Basically,
 the documentation and a lot of other things talk about every manage
 command having access to both --verbosity and --traceback, however doing a
 manage.py runserver --traceback has no effect, neither does manage.py
 runserver --verbosity=2.

 I think traceback in particular is necessary as anyone who is developing a
 RPC system using SOAP, AJAX, REST or any other four letter word can't see
 the literal exception that is taking place.

-- 
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.