-
Notifications
You must be signed in to change notification settings - Fork 148
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
Anthem not working with OCA Wheelhouse due to PIP problems #38
Comments
This has been worked on and solved by @sbidoul in acsone/odoo-autodiscover#3. |
@codingforfun I released odoo-autodiscover 2.0.0b1. |
I updated my example branch above. It's as simple as adding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to integrate the OCA approach of installing Odoo addons via pip instead of importing external source repositories.
More about this can be found here and here.
Also I prepared a minimal example based on https:/camptocamp/test-odoo-project demonstrating this for the example of installing
disable_odoo_online
from OCA server-tools here: camptocamp/test-odoo-project@master...codingforfun:pip-issuehttps:/codingforfun/test-odoo-project/tree/pip-issue
I run into the problem that anthem isn't finding odoo anymore if requirements from requirements.txt inside the child container contain dependencies to Odoo.
The reason seams to be that Odoo gets installed in the parent container with 'pip install -e'.
I did some research but don't have any conclusion yet and hope you maybe have an idea. It seams to have something to do with namespace packages. Pip packaged Odoo modules adds
namespace_packages: ['odoo', 'odoo.addons']
inside setup.py for the module.I was able to run anthem inside the container again after removal of the corresponding nspkg.pth from dist-packages.
Some relevant references I found:
The error log I get from
docker-compose up --build
:The text was updated successfully, but these errors were encountered: