dpaste is a good tool if you have a long code sample or traceback that are giving you some problems. Usually when responding to the thread with a solution, the poster with copy the relevant snippet making the dpaste obsolete for further references. This might not always be the case, but for most of the time it is.
Pasting the code is not a good solution as emails dont indent very well and make it a lot harder to actually see what is going on in the code and where the problem may lie. ~Jakob On 3 Jun., 19:59, Jashugan <jashu...@gmail.com> wrote: > I get frustrated when I go to an older thread and someone has a link > to dpaste, but the paste no longer exists. The whole point of the > thread is to keep the solution of a particular issue available for > posterity (or at least for a year). Dpaste, by default, doesn't allow > for this[1]. > > I think using djangosnippets.org, or pastie.org, or simply pasting the > code into the body of the message would be a better solution. > > Thoughts? > > [1] - Yes, you can 'hold' a paste, but that feature is not enabled by > default, making it easy to forget about it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
