Skip to content

Conversation

@JonathanNEMRY
Copy link

This PR applies same changes than faide#14

cc @alexis-via

@lmignon
Copy link

lmignon commented Dec 22, 2016

@alexis-via @JonathanNEMRY I'll refactor a little bit more to avoid too much memory consumption..
I'll update the 2 PRS once done (V9 and V10)

res = fd.read()
self._postprocess_report(
res, model_instance.id, save_in_attachment)
return res, "." + self.ir_actions_report_xml_id.py3o_filetype
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fear you re-introduced the "double dot in filename" bug, that I fixed with this commit b702d15

Did you test it this PR and check the filenames of the py3o reports generated ?

@alexis-via
Copy link
Member

@lmignon OK. So I understand I should wait for more commits from you guys before merging this PR. Good luck for your optimisations.

@lmignon
Copy link

lmignon commented Dec 23, 2016

@alexis-via Yes you are right. The optimisation is to always use files in the generation process and only at the end load the file into memory since it's what odoo expect... In the same time it become possible to override the postprocess method if you need to add a digital signature to your generated document for exemple. The posprocess mehod will be proposed to odoo on 'report' and if accepted by odoo we finally have a point of extension also for the generated qweb reports. You can also see that when the report is launched on a set of records I return a merged pdf if the result is pdf or a zip file with all the generated reports...

@lmignon
Copy link

lmignon commented Dec 23, 2016

@JonathanNEMRY @alexis-via My improvements are there... faide@9befca9
These should be tested (have done some but not enough)...
runbot is green

@alexis-via
Copy link
Member

Just drop me a note when I can merge. I'll have several go-live on 1st January with report_py3o, so if we merge this before Jan 1st, it will be a good "live test" :)

lmignon and others added 4 commits January 9, 2017 15:14
The goal is to improve the modularity by making the parser a true inheritable odoo model and share part of the code with the 'report' model

Conflicts:
	report_py3o/models/ir_actions_report_xml.py
	report_py3o/models/py3o_report.py
	report_py3o/tests/test_report_py3o.py
Conflicts:
	report_py3o/models/py3o_report.py
@JonathanNEMRY JonathanNEMRY force-pushed the 10.0-refactor_py3o-jne branch from 441483d to f592b75 Compare January 9, 2017 14:22
* flake8
@codecov-io
Copy link

codecov-io commented Jan 9, 2017

Current coverage is 77.51% (diff: 77.52%)

No coverage report found for 10-port-py3o at 5ac6710.

Powered by Codecov. Last update 5ac6710...4048c0b

@lmignon lmignon force-pushed the 10.0-refactor_py3o-jne branch from f7834fa to 9c82eec Compare January 25, 2017 11:14
@lmignon lmignon force-pushed the 10.0-refactor_py3o-jne branch from 9c82eec to 4048c0b Compare January 25, 2017 12:50
@alexis-via
Copy link
Member

@lmignon tell me when you want me to merge this.

@faide
Copy link

faide commented Feb 14, 2017

@lmignon sorry for the ping on the Wrong PR. Can we merge this one in the main PR ? or do you need more time on this ?

@lmignon
Copy link

lmignon commented Feb 14, 2017

@faide yes you can!
@alexis-via This one is ready to merge 😏

@alexis-via alexis-via merged commit 4aab7f9 into akretion:10-port-py3o Feb 14, 2017
@lmignon
Copy link

lmignon commented Feb 14, 2017

Merci @alexis-via !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants