banking-addons-team team mailing list archive

[Sébastien BEAU - http://www.akretion.com <sebastien.beau@xxxxxxxxxxxx>]

We need the try/catch because we want to raise an error in a pop up with all of the Error.
For example if some line of the bank statement file are incorrects, we want to raise a message with all of the exception. This avoid to the end User to try to import, have a error on the first wrong line, then fix it, try to import again, fix the second wrong line....again and again until eveyrthing is fix. With that try/catch you have an message with all of the error, you fix your file and it's ok.

Raising correctly all possible error with a python error and avoid re-catching code error can be a really good solution, but this need a lot of work, and I will have not time for it right now.

Maybe we can merge my work and we add a comment "that we should use python error for the next version", what do you think? It's better than nothing?
-- 
https://code.launchpad.net/~akretion-team/banking-addons/bank-statement-reconcile-70-debug-improvement/+merge/197771
Your team Banking Addons Core Editors is subscribed to branch lp:banking-addons/bank-statement-reconcile-7.0.