-
Notifications
You must be signed in to change notification settings - Fork 25.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[8.0] can't import dateparser from an Odoo module #10670
Comments
@alexis-via may be that's could help you understand what is going on: http://dangerontheranger.blogspot.com.br/2012/07/how-to-use-sysmetapath-with-python.html But yeah, at first sight I would say Odoo should have package_path=None instead in the signature, so it can cope with non Odoo calls and not match anything but that's probably fine. At least I would try that... |
@alexis-via should be fixed in the v8 branch (revision edeb5a8). It was our (Odoo's) fault: we setup a PEP302 import hook so that e.g. account can be imported as both It works in most cases because callers generally provide a Thanks for the report and sorry about that. |
@rvalyi @xmo-odoo @beledouxdenis Thank you very very much for your help and for the patch ! I updated my odoo v8 to the latest version (which includes your patch) and it works well now ! I can continue the development of my module account_invoice_import - a great module by the way, you should try it :) |
Here are the steps to reproduce the bug:
This is a real problem for me, because the lib invoice2data that is used in my module account_invoice_import (cf this PR OCA/account-invoicing#122) now uses dateparser, so, if you have the latest version of invoice2data, you won't be able to install the module account_invoice_import :-(
I don't know if this bug is Odoo's fault or dateparser's fault. I have some difficulty to understand the exact cause of the problem. One thing I noticed:
So I was thinking it may be mixing the two... but I really don't understand what's happening, so I may be completely wrong.
The text was updated successfully, but these errors were encountered: