Merge lp:~elbati/enapps-csv-import-tool/fix_file_to_list_method into lp:~enapps-london-uk/enapps-csv-import-tool/old_trunk
Proposed by
Lorenzo Battistini
Status: | Needs review | ||||||||
---|---|---|---|---|---|---|---|---|---|
Proposed branch: | lp:~elbati/enapps-csv-import-tool/fix_file_to_list_method | ||||||||
Merge into: | lp:~enapps-london-uk/enapps-csv-import-tool/old_trunk | ||||||||
Diff against target: |
33 lines (+2/-16) 1 file modified
ea_import/ea_import_chain.py (+2/-16) |
||||||||
To merge this branch: | bzr merge lp:~elbati/enapps-csv-import-tool/fix_file_to_list_method | ||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lorenzo Battistini (community) | Disapprove | ||
Enapps Ltd OpenERP Partner London UK | Pending | ||
Review via email: mp+122890@code.launchpad.net |
Description of the change
This fixes bug 999180
replacing the custom procedure used by 'file_to_list' method with python 'csv' reader
To post a comment you must log in.
Unmerged revisions
- 6. By Lorenzo Battistini
-
[FIX] ea_import
Using csv module instead of custom procedure
Lorenzo: good point, but I'd get rid of file_to_list altogether like in my previously proposed patch; if the method body fits on one line, there's no point in keeping the method around. Although one could also argue your version is more readable..
But anyway, Enapps doesn't accept merge proposals through launchpad. They use LP only to publish their work. Development happens on an internal git repo, and I'd guess the codebase on LP is probably outdated already.
You might want to check out my fully_patched branch of this project. That's one has all my patches, and is still updated whenever I find a new bug (although I'm using it less now, so not finding many bugs anymore). It can be found here: lp:~jri-openerp/enapps-csv-import-tool/fully-patched