Eric Hawthorne schrieb: > Whenever there is a problem in some python used within a kid template > (say, foo.kid), > I'm always stuck guessing at what line in the template is > being referred to in the error dump, because the stacktrace identifies > some line number in foo.py > and, fool that I am, I don't know where to find the generated foo.py and > I even suspect that > it is only in memory somewhere, because on disk I only see .pyc files > with the kid files. > > Maybe an easy question, but where are the .py files, or is there a debug > mode somewhere > that will send them to real files so I can debug them?
Set the environemt variable KID_OUTPUT_PY. Then the py files are not deleted. If you on *nix type in the bash: export KID_OUTPUT_PY=1 Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
