On 7/19/07, Stefan Matthias Aust <[EMAIL PROTECTED]> wrote: > > Is this something I should file an issue for? > > The Django debug HTML page is great for finding bugs in templates and > view functions. However, if you have an error in a view function with > a request object that contains a - say - 200MB file object, well, then > your browser dies a slow and painful death. At least my trusted > Firefox does.
To the best of my knowledge, this isn't currently configurable. However, it sounds like a reasonable suggestion. Feel free to log a ticket. Or even a fix, if you're feeling so enthused. It shouldn't be too difficult to implement. > And I wish it would be possible to edit the shown code just in place > :) What I know about Python so far, this should be possible, > shouldn't it? If you can load and display the source code, you must be > able to save a modified version to the same location... This is probably a little harder than you think. You have to get the code back up to the server, and reload the module. Depending on how you are deployed, you may need to restart a web server. Plus, you've just exposed a live, editable connection to your source code - which is a teeny tiny security risk :-) > And, well, syntax coloring would be nice... no just kidding... And a pony. :-) Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
