Archives
Contributors
-
Re: Becoming a PSC of OCA/storage
+1 for Laurent!On Fri, Oct 18, 2019 at 4:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:+1On Fri, Oct 18, 2019 at 1:22 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:HiI would like to propose myself as PSC/Maintainer of OCA/storage. I'm an active contributor on this repo and only @sebastienbeau is part of this PSC at this moment.Regardslmi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director 
Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
by Jay Vora - 01:31 - 18 Oct 2019 -
Re: Becoming a PSC of OCA/storage
+1On Fri, Oct 18, 2019 at 1:22 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:HiI would like to propose myself as PSC/Maintainer of OCA/storage. I'm an active contributor on this repo and only @sebastienbeau is part of this PSC at this moment.Regardslmi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu
by Denis Roussel - 01:26 - 18 Oct 2019 -
Re: Becoming a PSC of OCA/storage
+1On Fri, Oct 18, 2019 at 1:22 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:HiI would like to propose myself as PSC/Maintainer of OCA/storage. I'm an active contributor on this repo and only @sebastienbeau is part of this PSC at this moment.Regardslmi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 01:26 - 18 Oct 2019 -
Becoming a PSC of OCA/storage
HiI would like to propose myself as PSC/Maintainer of OCA/storage. I'm an active contributor on this repo and only @sebastienbeau is part of this PSC at this moment.Regardslmi
by Laurent Mignon - 01:21 - 18 Oct 2019 -
Re: Odoo to Odoo data migration tools
Hi all,We have simple library that allows to transfer data between Odoo databases via XML-RPC or JSON-RPC.All you need is to define transfer schema and run data-transfer.It was used to transfer data (sales and purchases) from Odoo 7.0 to Odoo 9.0This library is available here: https://github.com/crnd-inc/odoo-transfer-libвт, 15 жовт. 2019 о 20:42 Graeme Gellatly <gdgellatly@gmail.com> пише:The first generation would be fine of anygrate IF there arent too many duplicate records requiring discrimination you could get it all done in a just a few attempts. Config file the lot. I have an advanced fork of it somewhere optimized for speed and this kind of case, although I never tried it for merging multiple companies it should work.Main issue will be computed tree fields and sequences which will have to be dropped and recreated. Plus id sequences bumped. Ir property can also be a bit tricky.On Wed, 16 Oct 2019, 2:51 AM Daniel Reis, <dreis.pt@hotmail.com> wrote:Hello,
I have more than one customer request to merge several single-company databases into a single multi-company database.
The usual approaches all mean some level of data loss.
Since the database schemas are the same, I’m wondering if it would be feasible to have a tool that would copy the data at the database level, while properly handling the record ids conversion.
I’ve worked before with a tool that deal with that kind of problem – Anybox’s Anygrate.
So I could have a try at a second generation of that tool.
I wonder about other ideas?
Thanks
Daniel Reis
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dmytro.katyukha - 11:41 - 16 Oct 2019 -
Re: Odoo to Odoo data migration tools
The first generation would be fine of anygrate IF there arent too many duplicate records requiring discrimination you could get it all done in a just a few attempts. Config file the lot. I have an advanced fork of it somewhere optimized for speed and this kind of case, although I never tried it for merging multiple companies it should work.Main issue will be computed tree fields and sequences which will have to be dropped and recreated. Plus id sequences bumped. Ir property can also be a bit tricky.On Wed, 16 Oct 2019, 2:51 AM Daniel Reis, <dreis.pt@hotmail.com> wrote:Hello,
I have more than one customer request to merge several single-company databases into a single multi-company database.
The usual approaches all mean some level of data loss.
Since the database schemas are the same, I’m wondering if it would be feasible to have a tool that would copy the data at the database level, while properly handling the record ids conversion.
I’ve worked before with a tool that deal with that kind of problem – Anybox’s Anygrate.
So I could have a try at a second generation of that tool.
I wonder about other ideas?
Thanks
Daniel Reis
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 07:40 - 15 Oct 2019 -
Re: New library to migrate Odoo module code "odoo-migrate"
Hi all,First thanks all for your enthusiasm !About the name, OK to rename it. I'm not sure that if you want to rename the lib, or the command. For exemple, for git aggregator feature. The lib is named git-aggregator, and the command is gitaggregate. Can we continue the discussion here ?About the repository, if I understand correctly, it should be great to be under OCA umbrella, and in a stand-alone repository as proposed by Pedro and Stephane bidoul. Let's go renaming first, and moving owner of the lib after.The last week-end, I worked to integrate tests. Now, it includes tests that checks that initial V8 module are correctly migrated in V13. So I guess that it allows people to contribute avoiding regression.I also added tools to log (warning, error) if the migrated module depends on obsolete module based on the OpenUpgrade documentation.About the evolution, david Arnold, I did not feel the need to use pybowler for the time being, but feel free to make a Pull request using pybowler, if you want.Kind regards.Le lun. 14 oct. 2019 à 17:37, David Arnold <dar@xoe.solutions> a écrit :PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:Hi Silvain,there was coming something to my mind, I'd like to share.Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.Like regex without the "regular" in it.It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.Here are some example transform script: https://gist.github.com/blaggacao/13cf79fad489bca962e4a43eb580e9ee#file-logging-not-lazy-pyBased on facebook's excellent pybowler library.Best Regards,David A.On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:+1 stephane comment about standalone+1 about resist feature creepHasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?There is python-xmlsig and python-xades from Eric and many others too.El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:Nice! Thanks Sylvain.+1 for standalone project as well :)On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:+1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!-sbiOn Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:génialLe jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :Dear OCA Contributors,I am working on a migration from 8.0 to 12.0.For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the commandpip3 install odoo-migrateOnce installed, you can run the following command (other options are available)odoo-migrate -m my_module_name -i 8.0 -t 12.0It is based on the OCA recommendations available on this wiki.In addition to performing recurring operations,- it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)- it calls black for recent version- it realize commits1) If you're interested by such tool, you can review or test this project.2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.3) if some OCA members are OK, I can transfer this project under OCA umbrella.thank you for your feedback.kind regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sylvain LE GAL - 07:00 - 14 Oct 2019 -
XSLT for Odoo Studio
Hi Folks,I wrote a little stylesheet to transform Odoo Studio prototypes into raw python code.If you are interested,- please check it out
- propose improvements
You can find it here: https://gist.github.com/blaggacao/e7ba05c7b4aa36317046ceb843cbed9fBR,David A.
by dar - 05:50 - 14 Oct 2019 -
Re: Linting for 13.0 branches (using black and pre-commit)
Yeah! +1On how to enforce proper commit messages, too.And for branch naming convention: https://github.com/xoe-labs/pre-commitOn Mon, Oct 14, 2019 at 4:42 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,The new configurations are in place for the 13.0 branches.The blog post has all the details.Side note: the travis configuration has been reset to default on all 13.0 branches, so if there was a specific config for your repo, it needs to be reapplied manually as the module are migrated.Let us know of any issue / question.Enjoy!-sbiOn Tue, Oct 8, 2019 at 9:56 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:+1
MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANTO: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 
On Tue, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 from "Numigiens"Have a good day from Canada!
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :Dear contributors,Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:- run Black before committing your code on the 13.0 branches
- sort imports (stdlib, odoo, odoo.addons, local imports)
- To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
If you are interested in practical details and the rationale, read on.pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:- installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
- you then run "pre-commit install" after cloning a repository
- lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
- some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
- all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
- a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
The proposed configuration includes the following linters:- black, with default options (to facilitate usage)
- auto fix trailing whitespace
- auto fix newline at end of files
- detect debug statements
- flake8 with same options as before (except line length which is now the 88 black default)
- pyupgrade, to encourage python 3 idioms
- pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
- pylint with all checks (optional + mandatory), not failing
- isort to automatically sort imports (except in __init__.py where import order might be significant)
- run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,- checkout these branches
- run 'pre-commit install'
- start committing lint failures to see the effect.
If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/filesIn practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.Looking forward to reading your feedback.Best regards,-sbi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dar - 05:41 - 14 Oct 2019 -
Re: New library to migrate Odoo module code "odoo-migrate"
PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:Hi Silvain,there was coming something to my mind, I'd like to share.Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.Like regex without the "regular" in it.It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.Here are some example transform script: https://gist.github.com/blaggacao/13cf79fad489bca962e4a43eb580e9ee#file-logging-not-lazy-pyBased on facebook's excellent pybowler library.Best Regards,David A.On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:+1 stephane comment about standalone+1 about resist feature creepHasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?There is python-xmlsig and python-xades from Eric and many others too.El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:Nice! Thanks Sylvain.+1 for standalone project as well :)On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:+1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!-sbiOn Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:génialLe jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :Dear OCA Contributors,I am working on a migration from 8.0 to 12.0.For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the commandpip3 install odoo-migrateOnce installed, you can run the following command (other options are available)odoo-migrate -m my_module_name -i 8.0 -t 12.0It is based on the OCA recommendations available on this wiki.In addition to performing recurring operations,- it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)- it calls black for recent version- it realize commits1) If you're interested by such tool, you can review or test this project.2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.3) if some OCA members are OK, I can transfer this project under OCA umbrella.thank you for your feedback.kind regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dar - 05:36 - 14 Oct 2019 -
Re: New library to migrate Odoo module code "odoo-migrate"
Hi Silvain,there was coming something to my mind, I'd like to share.Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.Like regex without the "regular" in it.It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.Here are some example transform script: https://gist.github.com/blaggacao/13cf79fad489bca962e4a43eb580e9ee#file-logging-not-lazy-pyBased on facebook's excellent pybowler library.Best Regards,David A.On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:+1 stephane comment about standalone+1 about resist feature creepHasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?There is python-xmlsig and python-xades from Eric and many others too.El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:Nice! Thanks Sylvain.+1 for standalone project as well :)On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:+1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!-sbiOn Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:génialLe jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :Dear OCA Contributors,I am working on a migration from 8.0 to 12.0.For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the commandpip3 install odoo-migrateOnce installed, you can run the following command (other options are available)odoo-migrate -m my_module_name -i 8.0 -t 12.0It is based on the OCA recommendations available on this wiki.In addition to performing recurring operations,- it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)- it calls black for recent version- it realize commits1) If you're interested by such tool, you can review or test this project.2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.3) if some OCA members are OK, I can transfer this project under OCA umbrella.thank you for your feedback.kind regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dar - 05:31 - 14 Oct 2019 -
RE: Runbot restart
Thank you Alexandre
De: Stéphane Bidoul [mailto:stephane.bidoul@acsone.eu]
Enviado el: lunes, 14 de octubre de 2019 11:07
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Runbot restartThanks Alexandre for maintaining this critical part of our infrastructure!
-sbi
On Sun, Oct 13, 2019 at 9:31 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
Hello all,
I'm performing a server update on the runbot servers this morning. This
will require a reboot of the servers. Recent builds will be manually
rebuilt, but this will take a little time to get back.
Thanks for your patience.
--
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30
Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France
http://www.camptocamp.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 12:55 - 14 Oct 2019 -
Re: Linting for 13.0 branches (using black and pre-commit)
Dear contributors,The new configurations are in place for the 13.0 branches.The blog post has all the details.Side note: the travis configuration has been reset to default on all 13.0 branches, so if there was a specific config for your repo, it needs to be reapplied manually as the module are migrated.Let us know of any issue / question.Enjoy!-sbiOn Tue, Oct 8, 2019 at 9:56 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:+1
MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANTO: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 On Tue, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 from "Numigiens"Have a good day from Canada!Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :Dear contributors,Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:- run Black before committing your code on the 13.0 branches
- sort imports (stdlib, odoo, odoo.addons, local imports)
- To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
If you are interested in practical details and the rationale, read on.pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:- installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
- you then run "pre-commit install" after cloning a repository
- lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
- some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
- all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
- a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
The proposed configuration includes the following linters:- black, with default options (to facilitate usage)
- auto fix trailing whitespace
- auto fix newline at end of files
- detect debug statements
- flake8 with same options as before (except line length which is now the 88 black default)
- pyupgrade, to encourage python 3 idioms
- pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
- pylint with all checks (optional + mandatory), not failing
- isort to automatically sort imports (except in __init__.py where import order might be significant)
- run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,- checkout these branches
- run 'pre-commit install'
- start committing lint failures to see the effect.
If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/filesIn practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.Looking forward to reading your feedback.Best regards,-sbi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 11:41 - 14 Oct 2019 -
Re: Runbot restart
Thanks Alexandre for maintaining this critical part of our infrastructure!-sbiOn Sun, Oct 13, 2019 at 9:31 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
Hello all, I'm performing a server update on the runbot servers this morning. This will require a reboot of the servers. Recent builds will be manually rebuilt, but this will take a little time to get back. Thanks for your patience. -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 11:05 - 14 Oct 2019 -
Re: Runbot restart
ThanksLe lun. 14 oct. 2019 à 02:22, Moises Lopez <moylop260@vauxoo.com> a écrit :Thank you!--On Sun 13 Oct 2019 at 11:57 Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:Thank you 👍El dom., 13 de octubre de 2019 10:37, Frederik Kramer <frederik.kramer@initos.com> escribió:Thanks a lot Alexandre Best and nice rest of this sunday Frederik Am Sonntag, den 13.10.2019, 11:07 +0000 schrieb Alexandre Fayolle: > Maintenance is over, recent branches are being rebuilt. > > Have a nice sunday. > > Alexandre > > On 13/10/2019 09:28, Alexandre Fayolle wrote: >
> > Hello all, > > > > > > I'm performing a server update on the runbot servers this morning. > This > > > will require a reboot of the servers. Recent builds will be > manually > > > rebuilt, but this will take a little time to get back. > > > > > > Thanks for your patience. > > > > > > > > > > -- > Alexandre Fayolle > Chef de Projet > Tel : +33 4 58 48 20 30 > > Camptocamp France SAS > 18 rue du Lac Saint André > 73 370 Le Bourget-du-Lac > France > > http://www.camptocamp.com > _______________________________________________ > 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.comWeb: 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 10:51 - 14 Oct 2019 -
Re: Accounting: writing on debit/credit fields
Yes, it's present. I'm not planning to do it, but anyone can.Regards.
by Pedro M. Baeza - 09:41 - 14 Oct 2019 -
Re: Accounting: writing on debit/credit fields
Hi Pedro,Is this issue present in v11 (OCA/OCB)? If so, are you planning on backporting? Thanks.Regards.El sáb., 12 oct. 2019 a las 14:21, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Luis J. Salvatierra - Binovo IT Human Project S.L.
Astigarraga bidea 2, 2ª Izquierda, Oficina 10-11
20180 Oiartzun
Gipuzkoa, España
Teléfono: +34943569206
Web: https://www.binovo.es
by Luis J. Salvatierra - 09:20 - 14 Oct 2019
