Archives
Contributors
Re: 14.0 branches
Certainly not opinionated very much on this, i remember the "outdated library issue" in many many Java Enterprise Applications installations out there and i have the feeling that this is significantly easier to run into if you use a merely PIP approach on Odoo deployments as well but i might be wrong on this one. On the other hand there may be advantages for auditability of ERP systems if you use PIP Best Frederik Am Montag, den 12.10.2020, 20:31 +0000 schrieb Graeme Gellatly: > Hi, > > Honestly I tried both ways. Trying to have nice neat build OCA > installing modules. I even setup own Pypi server to distribute client > modules. This is basically how the pip workflow worked. > > pip install some_module > Oh it has a bug and I need to make a PR. > pip uninstall some_oca_module > git clone OCA/Web > git-aggregator file while PR waiting. > > pip install some_other_module > rinse repeat. > > Felt like every single module. Now maybe in a pure deployment > environment pip works, maybe once a release is mature it does too and > maybe I am a dinosaur and my workflow using git is stupid, but I just > don't like using the python packaging for Odoo. Just too much stuff > from too many different places. And unless every module you want to > use is pip available then it just feels like 2 different processes > even when there are no issues. > > On Tue, Oct 13, 2020 at 9:12 AM Nhomar Hernández <nhomar@vauxoo.com> > wrote: > > Hello Daniel. > > > > Yes I understand. > > > > AFAIK there is a problem with the version in pip. > > > > How do you cohexsists 14-13-12-11 in the same environment? > > How do you manage to do "from odoo import odoo" and falling > > apart virtualenv, how do you manage such coexistence? > > > > I am pretty sure it is out of the scope from odoo (but they are not > > closed to do it) because the owner of the pip package is vauxoo. > > > > https://pypi.org/project/odoo/ > > > > Olivier asked us a few years ago to give it to them but then after > > a few conversations it was never a priority to them (but maybe that > > will change). > > > > Regards. > > > > PS: can you share the command to tray it from github? > > > > I tried several options and I can't get it to work. > > > > El lun., 12 de oct. de 2020 a la(s) 12:47, Daniel Reis ( > > dreis@opensourceintegrators.com) escribió: > > > On 12/10/2020 11:07, Nhomar Hernández wrote: > > > > Do you think Odoo will be pip-installable in some moment? > > > > > > > > > > Just clearing this one, yes it is, thanks to some key > > > contribution Stéphane made into the Odoo core. > > > > > > Actually, I'll have a talk at the OCA Days called "pip install > > > odoo": > > > https://odoo-community.org/event/oca-days-2020-online-training-and-learning-event-2020-10-15-2020-10-16-121/track/pip-install-odoo-61 > > > > > > I personally find it very convenient and use it everyday in my > > > dev environments. > > > (Don't ask me about using it in deployment, my infrastructure > > > team doesn't let me put a finger in their servers...). > > > > > > Thanks > > > Daniel > > > > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > > Post to: mailto:contributors@odoo-community.org > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 11:20 - 12 Oct 2020
Reference
-
14.0 branches
Dear fellow contributors,The 14.0 branches are being created as I post this message.They are initialized from our new template repository that was created during the OCA Days sprint back in May [1]. This template is essentially a refreshed version of the linter configurations we have in 13.0. This new mechanism should make it easier to apply improvements across all repos in the future.Special thanks to Jairo Llopis for his work on this topic.I plan to provide a detailed walkthrough of all this during my OCA Days talk next week [6]. In the meantime, here are a few important things to note.2. Travis installs dependencies with pip, including addons of other repos1. The project description in README.md must be updated manually by PSCs.Since our project-level README were manually maintained and updated over a long period, it is difficult to reliably extract the variable content from them. So they are created afresh, and PSC are invited to update the repo description within the dedicated section of README.md. Please do not change the header and footer manually.This mechanism (activated by MQT_DEP=PIP in .travis.yml) does not use oca_dependencies.txt nor requirement.txt. It relies on __manifest__.py to discover dependencies from the 'depends' and 'external_dependencies' keys. Dependent addons are installed from the OCA wheelhouse [3], and python libraries are installed from PyPI.The main expected benefits are:- less redundancy (the manifests are enough to discover dependencies)- reduce rippling effects to unrelated repos when an addon or python library does not install or misbehaves, since only the dependencies really needed by a repo are installedIf a PR depends on an unmerged addon or PR, create a file named test-requirements.txt at the repo root containing a line like this:odoo14-addon-{addon_name} @ git+https://github.com/OCA/{repo}@refs/pull/{PR}/head#subdirectory=setup/{addon_name}This mechanism has been tested on several repos in 13.0 and should be reliable. In case of problem, mention me in the PR and/or create an issue in OCA/maintainer-quality-tools repo. Alternatively, you can restore the old behaviour by removing the MQT_DEP=PIP line from .travis.yml. For the curious, the code of the new mechanism is in the OCA/m-q-t repo [4]3. If you need local changes to the dotfiles let's discuss themThere are variables in the dot files, including .travis.yml [2]. To update them, the best way is to install copier [5], run "copier update" from the repo root, and answer the questions.If you need other changes, you can apply them locally to resolve urgent situations, but that may make updates harder. So please open an issue in [1] to discuss if changes need to be made to the template.As usual, don't hesitate to let me know of any issue.That's all for now, folks. Happy migration!-sbi--
by Stéphane Bidoul - 09:21 - 8 Oct 2020