Doesn't give information about where parse errors occur
Bug #677672 reported by
James Westby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Aaron Bentley |
Bug Description
Hi,
Thanks for fixing the bug that meant the user got no information about what
the problem with their recipe was when they produce an invalid recipe.
However, it just gives the bare error message now, where it can provide the
line and column information of the problem.
Please provide that information too. Providing it in a non-textual way in addition
would be fantastic.
I suggest that you do this while making use of the new usage information on
errors.
I worked very hard to give good error messages from the parser, so please pass
that information on to the user, and let me know if more information could be
provided.
Thanks,
James
Related branches
lp://qastaging/~abentley/launchpad/better-recipe-errors
- Tim Penhey (community): Approve
-
Diff: 61 lines (+25/-7)3 files modifiedlib/lp/code/browser/sourcepackagerecipe.py (+1/-4)
lib/lp/code/browser/tests/test_sourcepackagerecipe.py (+23/-2)
utilities/sourcedeps.conf (+1/-1)
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: recipe |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-code: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r11992 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 11992>.