You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed, --pdb does not work if the error occurs when the file is first imported, only when the tasks are running. So, currently, this will work as expected:
fromjugimportTaskGenerator@TaskGeneratordefraise_error(n):
ifn>2:
# <------ error while executing the Tasks: you will be dropped into a debuggerraiseValueError()
foriinrange(10):
raise_error(i)
I suppose it is a reasonable request to have it work when the error occurs while importing, though.
Bugfix release
Full ChangeLog:
- Fix handling of `JUG_EXIT_IF_FILE_EXISTS` environmental variable
- Fix passing an argument to jug.main() function
- Extend `--pdb` to exceptions raised while importing the jugfile (issue #79)
I'd like to debug errors that occur when I run a jug script. However, adding the
--pdb
flag doesn't seem to have any effect.Am I misunderstanding the intended use of the
--pdb
option?(Many thanks for the software, it's great)
The text was updated successfully, but these errors were encountered: