Archives
Contributors
contributors@odoo-community.org
-
emergency maintenance on OCA server
Hello everyone, We have a faulty disk on the OCA server. I opened a support issue to get it replaced in the datacenter. This will result in a downtime of the server, and possibly some degraded performance while the RAID arrays get rebuild. Impacted services: * our Odoo instance * our webite * the translation platform * the OCA gitbot I'll keep you posted when we have more information about the time of the intervention. We thank you for your understanding. -- Alexandre Fayolle Senior Software Engineer 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
by Alexandre Fayolle - 01:01 - 16 Nov 2023-
Re: emergency maintenance on OCA server
Oups... Thanks Stéphane On 17/11/2023 10:31, Stéphane Bidoul wrote: > Thank you Alex for handling this yesterday during the night. > > I did a quick check this morning and restarted the services that had > failed since (runboat, oca-github-bot, simpleindex). > > Everything should be back to normal, now. > > Best regards, > > -sbi > > > On Fri, Nov 17, 2023 at 10:18 AM Simone Orsi > <notifications@odoo-community.org > <mailto:notifications@odoo-community.org>> wrote: > > I think we have a problem w/ https://wheelhouse.odoo-community.org > <https://wheelhouse.odoo-community.org> for the builds > > On Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza > <notifications@odoo-community.org > <mailto:notifications@odoo-community.org>> wrote: > > Thank you very much for the work, Alexandre. > > It seems that runboat and the OCA bot still have some problems. > Can you please check? > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > <mailto:contributors@odoo-community.org> > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > > > > -- > Simone Orsi > > Full stack Python web developer, Odoo specialist, Odoo Community > Board Member, in love with open source. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > <mailto:contributors@odoo-community.org> > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer 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
by Alexandre Fayolle - 01:56 - 17 Nov 2023 -
Re: emergency maintenance on OCA server
Everything seems to be working now, thanks!Regards.
by Pedro M. Baeza - 11:35 - 17 Nov 2023 -
Re: emergency maintenance on OCA server
Thank you Alex for handling this yesterday during the night.I did a quick check this morning and restarted the services that had failed since (runboat, oca-github-bot, simpleindex).Everything should be back to normal, now.Best regards,-sbiOn Fri, Nov 17, 2023 at 10:18 AM Simone Orsi <notifications@odoo-community.org> wrote:I think we have a problem w/ https://wheelhouse.odoo-community.org for the buildsOn Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:Thank you very much for the work, Alexandre.It seems that runboat and the OCA bot still have some problems. Can you please check?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
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 - 10:30 - 17 Nov 2023 -
Re: emergency maintenance on OCA server
I think we have a problem w/ https://wheelhouse.odoo-community.org for the buildsOn Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:Thank you very much for the work, Alexandre.It seems that runboat and the OCA bot still have some problems. Can you please check?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi. - 10:16 - 17 Nov 2023
-
-
Manual Currency Conversion Bank Transaction
Hi everyone,I have the case of a client who wants that when importing a bank statement, in the reconciliation of movements thanks to the `account_reconciliation_widget` module, he can determine the rate that he agreed with his bank and not the one offered by Odoo.I'm surprised that there is no module for this, since it is very common.
I am trying to develop the functionality, but it is a bit complex to avoid the odoo rate and make everything add up in the end, since the rate calculation is repeated in several places.Any ideas or suggestions?Greetings and thank you very much,/Lansana Barry
by Lansana Barry - 09:25 - 16 Nov 2023-
Re: Manual Currency Conversion Bank Transaction
You need to use the bank-statement-import modules that you can find onIf the format is related to a localizatiion configuration, the exact module might be on the localization repoistory.Kind regards,El jue, 16 nov 2023 a las 9:26, Lansana Barry Sow (<notifications@odoo-community.org>) escribió:Hi everyone,I have the case of a client who wants that when importing a bank statement, in the reconciliation of movements thanks to the `account_reconciliation_widget` module, he can determine the rate that he agreed with his bank and not the one offered by Odoo.I'm surprised that there is no module for this, since it is very common.
I am trying to develop the functionality, but it is a bit complex to avoid the odoo rate and make everything add up in the end, since the rate calculation is repeated in several places.Any ideas or suggestions?Greetings and thank you very much,/Lansana Barry_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 09:36 - 16 Nov 2023
-
-
Odoo Test framework and rollback issue
Hi everyone,I'm currently developing on 14.0 a test for one of my module and I'm having a headache trying to understand why an action is not properly rolled back after the exception is raised.My code sample:class TestSoftwareLicensePass(TransactionCase):
def test_activation(self):
...
self.assertEqual(pass_lic1.get_remaining_activation(), 1)
with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
pass_lic1.activate("device_uuid_4/3")
self.assertEqual(pass_lic1.get_remaining_activation(), 1)
with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
pass_lic1.activate("device_uuid_4/3")The second assertEqual statement FAILS because get_remaining_activation() returns 0, but since the exception has been correctly captured by the with self.assertRaisesRegex statement, this part should have been rolled back by the odoo framework.(and no cr.commit in the activate function)Looking in other tests, I can see that a lot of with self.assert statements have a self.cr.savepoint() at their side (like this code sample in odoo/odoo/addons/base/tests/test_views.py):
class TestViewInheritance(ViewCase):def test_no_recursion(self):
r1 = self.makeView('R1')
with self.assertRaises(ValidationError), self.cr.savepoint():
r1.write({'inherit_id': r1.id})Is this related to the TransactionCase class ? (Probably not, I made a test with SavepointCase and same issue)Should I always append self.cr.savepoint() ?Yann.
by Yann Papouin - 06:16 - 15 Nov 2023-
Re: Odoo Test framework and rollback issue
Thank you all for your feedback.So I will (when possible) try to split my tests and re-arrange their content so that the exception assertions are (is) processed at the very end.Anyway, I will always add the self.cr.savepoint() in the with context (looking at the Odoo 14.0 code, clear_upon_failure is automatically called by assertRaises).--
Yann PAPOUINLe ven. 17 nov. 2023 à 13:42, Pedro M. Baeza <notifications@odoo-community.org> a écrit :Holger Brunn has pointed to me that there's a way to recover properly in SavepointCase tests after a raise:You have to add the reset_on_failure to your `with` statement. And it seems that since v15, the savepoint is enough.Anyway, think twice about piling a lot of asserts in the same test, being raise or not, as having an early failure makes you to iterate several times until having a pass one, although testing flows is usual to have that sequential asserts.Thanks for the extra insights, Holger!Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yann Papouin - 02:51 - 23 Nov 2023 -
Re: Odoo Test framework and rollback issue
Holger Brunn has pointed to me that there's a way to recover properly in SavepointCase tests after a raise:You have to add the reset_on_failure to your `with` statement. And it seems that since v15, the savepoint is enough.Anyway, think twice about piling a lot of asserts in the same test, being raise or not, as having an early failure makes you to iterate several times until having a pass one, although testing flows is usual to have that sequential asserts.Thanks for the extra insights, Holger!Regards.
by Pedro M. Baeza - 01:41 - 17 Nov 2023 -
Re: Odoo Test framework and rollback issue
Hi,In Odoo 14, you should append self.cr.savepoint() when you want to add additional tests after the assertRaises. It's required to restore the db cursor, the environment and the cache at the state prior to the exception. You should also question why you want to add additional tests after this assertion? Maybe they can be put into another specific test method. In Odoo 16 (at least), odoo overrides the assertRaises method to add the call to the savepoint and ensures a cleanup of the environment. https://github.com/odoo/odoo/blob/16.0/odoo/tests/common.py#L367Regards,lmiOn Wed, Nov 15, 2023 at 6:24 PM Yann Papouin <notifications@odoo-community.org> wrote:Hi everyone,I'm currently developing on 14.0 a test for one of my module and I'm having a headache trying to understand why an action is not properly rolled back after the exception is raised.My code sample:class TestSoftwareLicensePass(TransactionCase):
def test_activation(self):
...
self.assertEqual(pass_lic1.get_remaining_activation(), 1)
with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
pass_lic1.activate("device_uuid_4/3")
self.assertEqual(pass_lic1.get_remaining_activation(), 1)
with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
pass_lic1.activate("device_uuid_4/3")The second assertEqual statement FAILS because get_remaining_activation() returns 0, but since the exception has been correctly captured by the with self.assertRaisesRegex statement, this part should have been rolled back by the odoo framework.(and no cr.commit in the activate function)Looking in other tests, I can see that a lot of with self.assert statements have a self.cr.savepoint() at their side (like this code sample in odoo/odoo/addons/base/tests/test_views.py):
class TestViewInheritance(ViewCase):def test_no_recursion(self):
r1 = self.makeView('R1')
with self.assertRaises(ValidationError), self.cr.savepoint():
r1.write({'inherit_id': r1.id})Is this related to the TransactionCase class ? (Probably not, I made a test with SavepointCase and same issue)Should I always append self.cr.savepoint() ?Yann._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Laurent Mignon - 08:51 - 16 Nov 2023 -
Re: Odoo Test framework and rollback issue
It's just a problem with how Odoo handles rollbacks and savepoints in tests. The thumb rule is to not do anything more after testing a raise. Do it in another test method.Regards.
by Pedro M. Baeza - 07:47 - 15 Nov 2023
-
-
Sale/invoice report break page
Dear community,One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.Do you know any existing modules to do that ?As sections are table rows it's not as easy to add apage-break-inside: avoid;on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.This probably ends up with 3 modules:base_breakpage in oca/reporting-enginesale_report_breakpage in oca/sale-reportingaccount_invoice_report_breakpage in oca/account-invoice-reportingAny hints on that ?regards
by Pierre Verkest - 11:36 - 15 Nov 2023-
Re: Sale/invoice report break page
Hi there,tl;dr: 3 new PRs to reviews to get more control on page breaks in sales/invoices PDF report* report_qweb_table_pagebreak: https://github.com/OCA/reporting-engine/pull/826:Control Page Breaks in `<table>`'s within QWeb ReportsThe primary objective of this module is to prevent tables
from being split arbitrarily and to provide better control
over page breaks within tables.* sale_report_pagebreak: https://github.com/OCA/sale-reporting/pull/243:Avoid break page inside sections on sale PDF report* account_report_pagebreak: https://github.com/OCA/account-invoice-reporting/pull/297:Avoid break page inside sections on invoice PDF reportOn the way to create those modules I got few challenges to I change a bit the behaviour on this first version* `page-break-[before|afeter|inside]` only applies on block elements which `<tr>` aren't by default, that whythe first PR `report_qweb_table_pagebreak` is splitting table and manage page break at <table> level* adding new kind of line (like note or section) on sale order line or account move line would be the bestbehaviour I would implement as expected behaviour for end user but I'm a bit scared about the impacton existing code to ignore those lines so I forgot that idea (I haven't test to be honest)* adding a boolean field on sale order line is pretty straightforward except for section where we should implementa widget to allow to manage the attribute from the form viewSo I end up with this first solution which will try to avoid breaking pages inside each section which could be improvedlater to give even more control.Cheers,Le mer. 15 nov. 2023 à 19:52, Tom Blauwendraat <notifications@odoo-community.org> a écrit :Hey Pierre,
only thing I know is that it's possible to manually add "page-break-before: always;" to certain elements. So once you know how many rows fit on a page, you could adjust the QWEB generation to add page breaks at the right places. This doesn't take into account page margins however, so probably your way is better.
-Tom
On 11/15/23 11:38, Pierre Verkest wrote:
Dear community,
One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.
Do you know any existing modules to do that ?
As sections are table rows it's not as easy to add apage-break-inside: avoid;on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.
This probably ends up with 3 modules:
base_breakpage in oca/reporting-enginesale_report_breakpage in oca/sale-reportingaccount_invoice_report_breakpage in oca/account-invoice-reporting
Any hints on that ?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
--Pierre
by Pierre Verkest - 06:11 - 13 Dec 2023 -
Re: Sale/invoice report break page
Hey Pierre,
only thing I know is that it's possible to manually add "page-break-before: always;" to certain elements. So once you know how many rows fit on a page, you could adjust the QWEB generation to add page breaks at the right places. This doesn't take into account page margins however, so probably your way is better.
-Tom
On 11/15/23 11:38, Pierre Verkest wrote:
Dear community,
One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.
Do you know any existing modules to do that ?
As sections are table rows it's not as easy to add apage-break-inside: avoid;on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.
This probably ends up with 3 modules:
base_breakpage in oca/reporting-enginesale_report_breakpage in oca/sale-reportingaccount_invoice_report_breakpage in oca/account-invoice-reporting
Any hints on that ?regards
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 07:47 - 15 Nov 2023
-
-
unit price precision based on product UOM category selected
Hi,Is there a module that can help me with the following?use case: change the unit price precision based on the selected product's uom (or product category's uom)I add to a SO, invoice, PO:- a 1st line with an article with a UOM of type "energy" and this would allow me to specify the unit price with 4 digits- a 2nd line with an article with a UOM of type "unit" and this would allow me to specify the unit price with default 2 digits.Thank you--Yves Goldberg--
by Yves Goldberg - 09:21 - 15 Nov 2023-
Re: unit price precision based on product UOM category selected
Il giorno mer 15 nov 2023 alle ore 09:22 Yves Goldberg <notifications@odoo-community.org> ha scritto:Hi,Is there a module that can help me with the following?use case: change the unit price precision based on the selected product's uom (or product category's uom)I add to a SO, invoice, PO:- a 1st line with an article with a UOM of type "energy" and this would allow me to specify the unit price with 4 digits- a 2nd line with an article with a UOM of type "unit" and this would allow me to specify the unit price with default 2 digits.Thank you--Yves Goldberg--_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Francesco Foresti - 09:31 - 15 Nov 2023
-
-
intercompany transfer
dear alli have issue with inter companyi have to companies A&Bboth company sell and purchase from themwhen make this process between them i have in inventory tow delivery order or tow Receipts for one sales order or purchaseplease i need help to solve it--Best RegardsSamir Mahmoud00201062648111
by Samir Mahmoud Hassan - 03:30 - 14 Nov 2023-
Re: intercompany transfer
Hi, have you looked in repository https://github.com/OCA/multi-company , specifically module https://github.com/OCA/multi-company/tree/14.0/purchase_sale_inter_company ?CheersIl giorno mar 14 nov 2023 alle ore 15:32 Samir Hassan <notifications@odoo-community.org> ha scritto:dear alli have issue with inter companyi have to companies A&Bboth company sell and purchase from themwhen make this process between them i have in inventory tow delivery order or tow Receipts for one sales order or purchaseplease i need help to solve it--Best RegardsSamir Mahmoud00201062648111
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Francesco Foresti - 03:51 - 14 Nov 2023
-
-
Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
Dear community,I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to take or the process involved.Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.Best regards,Compassion Switzerland
by "Emanuel Cino" <emanuel@compassion.ch> - 12:29 - 13 Nov 2023-
Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
Well, you just need to create a Pull request and add yourself on the following file:Once the PR is merged by someone on the board, you will receive the notification :DEl lun, 20 nov 2023 a las 11:42, Cino, Emanuel (<notifications@odoo-community.org>) escribió:Thank you Yannick,What are the next steps for fulfilling my application? Please let me know and I will take the necessary steps.Have a great week!Emanuel CinoLe mar. 14 nov. 2023 à 15:01, Yannick Payot <notifications@odoo-community.org> a écrit :Hello Emanuel,+1 for your applicationI will gladly welcome you as a PSC member.Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.To synchronize it's important to keep the "Migration to XX" github issues up to date:All the best,YannickOn Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:Dear community,I hope this email finds y ou well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.Best regards,Compassion Switzerland
_______________________________________________
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
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 11:47 - 20 Nov 2023 -
Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
Hello Emanuel,+1 for your applicationI will gladly welcome you as a PSC member.Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.To synchronize it's important to keep the "Migration to XX" github issues up to date:All the best,YannickOn Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:Dear community,I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.Best regards,Compassion Switzerland_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yannick Payot - 03:00 - 14 Nov 2023
-
-
17.0 branches
Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/--Stéphane Bidoul
by Stéphane Bidoul - 04:18 - 12 Nov 2023-
Re: 17.0 branches
Thanks a lot Stéphane for all these evolutions.Some of them have a really good impact on the environment, double thanks for that.Le lun. 13 nov. 2023 à 15:52, Juan José Scarafía <notifications@odoo-community.org> a écrit :El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/--Stéphane Bidoul_______________________________________________
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 David BEAL - 07:25 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/--Stéphane Bidoul_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan José Scarafía - 03:51 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
It can be decided per branch answering the copier question.Regards.
by Pedro M. Baeza - 03:36 - 13 Nov 2023 -
Re: 17.0 branches
Will Ruff also be used on earlier branches or will it only be used for 17.0+?Il giorno dom 12 nov 2023 alle ore 17:25 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/--Stéphane Bidoul_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 03:31 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
Thanks StéphaneOn Sun, Nov 12, 2023 at 7:55 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/--Stéphane Bidoul_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Mostafa Barmshory - 03:28 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Looking for a module
Hi,use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".is there a module doing this to your knowledge?Thanks!
by Francesco Foresti - 11:01 - 10 Nov 2023-
Re: Looking for a module
Thanks Denis,we've found https://github.com/OCA/sale-workflow/tree/14.0/sale_partner_shipping_invoice_domain that seems to do what's requested (and opened a PR to fix readme here: https://github.com/OCA/sale-workflow/pull/2771 )CheersFrancescoIl giorno ven 10 nov 2023 alle ore 11:32 Roussel, Denis <notifications@odoo-community.org> ha scritto:Hi Francesco,Maybe you can look at https://github.com/OCA/sale-workflow/tree/14.0/sale_order_partner_restrictAn extension should maybe done.On Fri, Nov 10, 2023 at 11:02 AM Francesco Foresti <notifications@odoo-community.org> wrote:Hi,use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".is there a module doing this to your knowledge?Thanks!
_______________________________________________
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 Francesco Foresti - 12:01 - 10 Nov 2023 -
Re: Looking for a module
Hi Francesco,Maybe you can look at https://github.com/OCA/sale-workflow/tree/14.0/sale_order_partner_restrictAn extension should maybe done.On Fri, Nov 10, 2023 at 11:02 AM Francesco Foresti <notifications@odoo-community.org> wrote:Hi,use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".is there a module doing this to your knowledge?Thanks!_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Denis Roussel. - 11:32 - 10 Nov 2023
-
-
e-commerce category with images
Dear contributors,I've been asked for a way to render categories in e-commerce pretty much like brands in https://github.com/OCA/e-commerce/tree/14.0/website_sale_product_brandDo we have a module for this?Thanks--Francesco Ballerini
by Francesco Ballerini - 11:00 - 8 Nov 2023-
Re: e-commerce category with images
Thanks for quick response.Regards--Francesco BalleriniIl giorno mer 8 nov 2023 alle ore 11:07 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:I don't know any.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 11:15 - 8 Nov 2023 -
Re: e-commerce category with images
I don't know any.Regards.
by Pedro M. Baeza - 11:06 - 8 Nov 2023
-
-
DMS: uploading xml files bypassing svg mimetype
Dear contributors,I am using DMS module on odoo14 to implement some shared backend data storage.By the way thanks for sharing this module, it's a powerful resource.I have succeeded in uploading some XML files by python code and they are uploaded with an "image/svg+xml" mimetype: this is ok but causes "my_file.xml" to be downloaded in .svg format while I need them to be directly downloaded as .xml (extension is correctly computed as xml).At the moment a simple way to solve this is by inheriting mimetype computing function and forcing mimetype by using context when creating records from code in a specific workflow
@api.depends("content")
def _compute_mimetype(self):
super(File, self)._compute_mimetype()
for record in self:
force_mimetype = self.env.context.get("force_mimetype")
if force_mimetype:
record.mimetype = force_mimetype
Actually my guess is that any non-mapped odoo.tools mimetype will lead the "download" button to ignore the mimetype and download file with the proper extension. This also makes me think why "mimetype" has priority over the "extension" for download, but I am more interested to know if there is a proper way to avoid this behaviour.I am not confident with data upload from code so I am wondering if I'm missing something that can be done only in create method, without having to inherit the module source code.Best Regards--Francesco Ballerini
by Francesco Ballerini - 08:01 - 4 Nov 2023-
Re: DMS: uploading xml files bypassing svg mimetype
I answer myself: I forgot to install python-magic library which is not mandatory but advised in module documentation.It came back to me when I had to solve another issue, then I realized python-magic also helps to correctly compute xml mimetype to "text/xml".Best Regards--Francesco BalleriniIl giorno sab 4 nov 2023 alle ore 19:57 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:Dear contributors,I am using DMS module on odoo14 to implement some shared backend data storage.By the way thanks for sharing this module, it's a powerful resource.I have succeeded in uploading some XML files by python code and they are uploaded with an "image/svg+xml" mimetype: this is ok but causes "my_file.xml" to be downloaded in .svg format while I need them to be directly downloaded as .xml (extension is correctly computed as xml).At the moment a simple way to solve this is by inheriting mimetype computing function and forcing mimetype by using context when creating records from code in a specific workflow
@api.depends("content")
def _compute_mimetype(self):
super(File, self)._compute_mimetype()
for record in self:
force_mimetype = self.env.context.get("force_mimetype")
if force_mimetype:
record.mimetype = force_mimetype
Actually my guess is that any non-mapped odoo.tools mimetype will lead the "download" button to ignore the mimetype and download file with the proper extension. This also makes me think why "mimetype" has priority over the "extension" for download, but I am more interested to know if there is a proper way to avoid this behaviour.I am not confident with data upload from code so I am wondering if I'm missing something that can be done only in create method, without having to inherit the module source code.Best Regards--Francesco Ballerini
by Francesco Ballerini - 10:25 - 6 Nov 2023
-
-
Installing Odoo on ubuntu desktop is suitable for production?
Dear contributors,It would be really helpful to me if you can give me an hint on this.I premise I have very low experience with odoo maintenance as I'm generally engaged with developement area.I mantain a couple of very simple instances with ubuntu server but I need to build and be active in the mantainance process of a more complex instance, with e-Commerce logic involved.It's been an year I work on server version and I got used to it pretty much, despite that I wonder if it's really worth to lose GUI feature to save some resources for an Odoo instance, so I am considering dropping server version in favour of desktop.In the logic of an Odoo server mantainer is this crazy or fairly acceptable?Regards-----Francesco Ballerini
by Francesco Ballerini - 01:51 - 29 Oct 2023-
Re: Installing Odoo on ubuntu desktop is suitable for production?
I was aiming for that but I wasn't sure it was ok to put everything on the same machine, really nice to hear that's possible and also a good practice !Thanks @Pedro M. Baeza @Oleg KuryanIl giorno lun 30 ott 2023 alle ore 09:07 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:You can use as well a customized Docker version thought for keeping 3 environments at the same time: development, production and staging/demo.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 09:36 - 30 Oct 2023 -
Re: Installing Odoo on ubuntu desktop is suitable for production?
You can use as well a customized Docker version thought for keeping 3 environments at the same time: development, production and staging/demo.Regards.
by Pedro M. Baeza - 09:05 - 30 Oct 2023 -
Re: Installing Odoo on ubuntu desktop is suitable for production?
Francesco,
Docker is much easier as all needed scripts already inside. The best answer will be just to check official docs on docker hub. But there are lots and lots of videos and articles in internet https://hub.docker.com/_/odoo/
On Monday, October 30, 2023, Francesco Ballerini <notifications@odoo-community.org> wrote:Thanks, both feedback are really valuable.@Florian, no specific reasons except for the fact that GUI makes things easier sometimes, so I was wondering if the extra-effort (which is not much as soon as you get use to the "mantainance routine") was worth, basically.Sometimes I suffer from lacking enough experience to figure out my self: part of the reason is that Odoo is my "entry point" in the world of ERP/IT, which I started to be interest in only couple of years ago as developer, but never had time to put too much attention to server mantainance. In the past I have been told that server installation is basically a "must" for the same reason you listed... but I received this information from people who were not daily engaged with Odoo, so I was searching for a confirm or denial in the context of Odoo from community members.@Oleg Thank you, I will take time to look closely to this script. I think we will start to use docker soon, can run your script with no problem on a container is it right? Also do you reccomend something similar for docker?Regards------Francesco BalleriniIl giorno dom 29 ott 2023 alle ore 14:23 Florian Laporte <notifications@odoo-community.org > ha scritto:Fransesco,I would discourage using a desktop environment on any web server, Odoo or not.it would introduce a lot of unnecessary dependencies, disk usage, and daemons.More dependencies would also mean a potentially less secure system, just because there is more attack surface.Is there any specific reason you would prefer Ubuntu desktop?Sincerely,Florian LOn Sun, Oct 29, 2023, 13:52 Francesco Ballerini <notifications@odoo-community.org > wrote:Dear contributors,It would be really helpful to me if you can give me an hint on this.I premise I have very low experience with odoo maintenance as I'm generally engaged with developement area.I mantain a couple of very simple instances with ubuntu server but I need to build and be active in the mantainance process of a more complex instance, with e-Commerce logic involved.It's been an year I work on server version and I got used to it pretty much, despite that I wonder if it's really worth to lose GUI feature to save some resources for an Odoo instance, so I am considering dropping server version in favour of desktop.In the logic of an Odoo server mantainer is this crazy or fairly acceptable?Regards-----Francesco Ballerini______________________________
_________________
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
--///
Best Regards,
Oleg Kuryan
CEO & COO, VentorTech OÜ | Building Personalized Inventory and Product Management Systems
by "Oleg Kuryan" <oleg@ventor.tech> - 08:56 - 30 Oct 2023 -
Re: Installing Odoo on ubuntu desktop is suitable for production?
Thanks, both feedback are really valuable.@Florian, no specific reasons except for the fact that GUI makes things easier sometimes, so I was wondering if the extra-effort (which is not much as soon as you get use to the "mantainance routine") was worth, basically.Sometimes I suffer from lacking enough experience to figure out my self: part of the reason is that Odoo is my "entry point" in the world of ERP/IT, which I started to be interest in only couple of years ago as developer, but never had time to put too much attention to server mantainance. In the past I have been told that server installation is basically a "must" for the same reason you listed... but I received this information from people who were not daily engaged with Odoo, so I was searching for a confirm or denial in the context of Odoo from community members.@Oleg Thank you, I will take time to look closely to this script. I think we will start to use docker soon, can run your script with no problem on a container is it right? Also do you reccomend something similar for docker?Regards------Francesco BalleriniIl giorno dom 29 ott 2023 alle ore 14:23 Florian Laporte <notifications@odoo-community.org> ha scritto:Fransesco,I would discourage using a desktop environment on any web server, Odoo or not.it would introduce a lot of unnecessary dependencies, disk usage, and daemons.More dependencies would also mean a potentially less secure system, just because there is more attack surface.Is there any specific reason you would prefer Ubuntu desktop?Sincerely,Florian LOn Sun, Oct 29, 2023, 13:52 Francesco Ballerini <notifications@odoo-community.org> wrote:Dear contributors,It would be really helpful to me if you can give me an hint on this.I premise I have very low experience with odoo maintenance as I'm generally engaged with developement area.I mantain a couple of very simple instances with ubuntu server but I need to build and be active in the mantainance process of a more complex instance, with e-Commerce logic involved.It's been an year I work on server version and I got used to it pretty much, despite that I wonder if it's really worth to lose GUI feature to save some resources for an Odoo instance, so I am considering dropping server version in favour of desktop.In the logic of an Odoo server mantainer is this crazy or fairly acceptable?Regards-----Francesco Ballerini
_______________________________________________
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 Francesco Ballerini - 03:08 - 30 Oct 2023 -
Re: Installing Odoo on ubuntu desktop is suitable for production?
Fransesco,I would discourage using a desktop environment on any web server, Odoo or not.it would introduce a lot of unnecessary dependencies, disk usage, and daemons.More dependencies would also mean a potentially less secure system, just because there is more attack surface.Is there any specific reason you would prefer Ubuntu desktop?Sincerely,Florian LOn Sun, Oct 29, 2023, 13:52 Francesco Ballerini <notifications@odoo-community.org> wrote:Dear contributors,It would be really helpful to me if you can give me an hint on this.I premise I have very low experience with odoo maintenance as I'm generally engaged with developement area.I mantain a couple of very simple instances with ubuntu server but I need to build and be active in the mantainance process of a more complex instance, with e-Commerce logic involved.It's been an year I work on server version and I got used to it pretty much, despite that I wonder if it's really worth to lose GUI feature to save some resources for an Odoo instance, so I am considering dropping server version in favour of desktop.In the logic of an Odoo server mantainer is this crazy or fairly acceptable?Regards-----Francesco Ballerini_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by florian.laporte - 02:21 - 29 Oct 2023
-
-
Abandoning python 2, Odoo <= 10
Hi everyone,As time goes by, it becomes harder and harder to support very old and unsupported python versions, as libraries and tooling stop supporting it.Moreover, the growing number of branches place an increasing burden on our infrastructure (bot, weblate, etc).Therefore the board proposes to drop support for Python 2 and therefore Odoo <= 10.0.Concretely, this means the branches will remain available for ad-hoc collaboration or bug fixes, but we will stop maintaining tooling: CI (travis will soon be stopped), weblate sync, bot, publishing to PyPI etc.This may happen soon as we clean up things while preparing for Odoo 17. In the future we will consider having an explicit version support policy, but I suspect the main decision criteria will be tool maintenance burden.Best regards,-Stéphane
by Stéphane Bidoul - 06:30 - 27 Oct 2023-
Re: Abandoning python 2, Odoo <= 10
> you mention "bot", does this mean the OCA bot will no longer be useable to merge PRs?
At some point it will break down, yes, if only because CI will be red.
-sbi
On Tue, Nov 7, 2023 at 9:57 AM Alexandre Fayolle <notifications@odoo-community.org> wrote:Hello Stéphane, This is a good decision IMO. you mention "bot", does this mean the OCA bot will no longer be useable to merge PRs? Alexandre On 27/10/2023 18:32, Stéphane Bidoul wrote: > Hi everyone, > > As time goes by, it becomes harder and harder to support very old and > unsupported python versions, as libraries and tooling stop supporting it. > > Moreover, the growing number of branches place an increasing burden on > our infrastructure (bot, weblate, etc). > > Therefore the board proposes to drop support for Python 2 and therefore > Odoo <= 10.0. > > Concretely, this means the branches will remain available for ad-hoc > collaboration or bug fixes, but we will stop maintaining tooling: CI > (travis will soon be stopped), weblate sync, bot, publishing to PyPI etc. > > This may happen soon as we clean up things while preparing for Odoo 17. > In the future we will consider having an explicit version support > policy, but I suspect the main decision criteria will be tool > maintenance burden. > > Best regards, > > -Stéphane > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer 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 - 10:06 - 7 Nov 2023 -
Re: Abandoning python 2, Odoo <= 10
Hello Stéphane, This is a good decision IMO. you mention "bot", does this mean the OCA bot will no longer be useable to merge PRs? Alexandre On 27/10/2023 18:32, Stéphane Bidoul wrote: > Hi everyone, > > As time goes by, it becomes harder and harder to support very old and > unsupported python versions, as libraries and tooling stop supporting it. > > Moreover, the growing number of branches place an increasing burden on > our infrastructure (bot, weblate, etc). > > Therefore the board proposes to drop support for Python 2 and therefore > Odoo <= 10.0. > > Concretely, this means the branches will remain available for ad-hoc > collaboration or bug fixes, but we will stop maintaining tooling: CI > (travis will soon be stopped), weblate sync, bot, publishing to PyPI etc. > > This may happen soon as we clean up things while preparing for Odoo 17. > In the future we will consider having an explicit version support > policy, but I suspect the main decision criteria will be tool > maintenance burden. > > Best regards, > > -Stéphane > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer 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
by Alexandre Fayolle - 09:56 - 7 Nov 2023 -
Re: Abandoning python 2, Odoo <= 10
+1 it's time to move forward...On Fri, Oct 27, 2023 at 11:51 PM Francesco Apruzzese <notifications@odoo-community.org> wrote:Totally agree! +1Il ven 27 ott 2023, 18:32 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:Hi everyone,As time goes by, it becomes harder and harder to support very old and unsupported python versions, as libraries and tooling stop supporting it.Moreover, the growing number of branches place an increasing burden on our infrastructure (bot, weblate, etc).Therefore the board proposes to drop support for Python 2 and therefore Odoo <= 10.0.Concretely, this means the branches will remain available for ad-hoc collaboration or bug fixes, but we will stop maintaining tooling: CI (travis will soon be stopped), weblate sync, bot, publishing to PyPI etc.This may happen soon as we clean up things while preparing for Odoo 17. In the future we will consider having an explicit version support policy, but I suspect the main decision criteria will be tool maintenance burden.Best regards,-Stéphane
_______________________________________________
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 Laurent Mignon - 10:51 - 29 Oct 2023 -
Re: Abandoning python 2, Odoo <= 10
Totally agree! +1Il ven 27 ott 2023, 18:32 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:Hi everyone,As time goes by, it becomes harder and harder to support very old and unsupported python versions, as libraries and tooling stop supporting it.Moreover, the growing number of branches place an increasing burden on our infrastructure (bot, weblate, etc).Therefore the board proposes to drop support for Python 2 and therefore Odoo <= 10.0.Concretely, this means the branches will remain available for ad-hoc collaboration or bug fixes, but we will stop maintaining tooling: CI (travis will soon be stopped), weblate sync, bot, publishing to PyPI etc.This may happen soon as we clean up things while preparing for Odoo 17. In the future we will consider having an explicit version support policy, but I suspect the main decision criteria will be tool maintenance burden.Best regards,-Stéphane
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Apruzzese - 11:51 - 27 Oct 2023 -
Re: Abandoning python 2, Odoo <= 10
+1 for me. V10 is old enough. There's no sense on keeping "support" for older versions.El vie, 27 oct 2023 18:57, Pedro M. Baeza <notifications@odoo-community.org> escribió:Yes, it's needed. If someone wants to contribute some support though, it's always welcome.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Harald Panten Lopez - 10:46 - 27 Oct 2023
-
-
Looking for purchase module to filter vendors in PO
Hi,do you know if there is an OCA module setting a domain on field Vendor in PO to only allow selection of partners with supplier_rank != 0 ?I'm on 14 but will gladly back- or forward-port.
by Francesco Foresti - 04:06 - 27 Oct 2023-
Re: Looking for purchase module to filter vendors in PO
Il giorno ven 27 ott 2023 alle ore 16:43 Francesco Foresti <francesco.foresti@ooops404.com> ha scritto:Thanks, that's a good starting point!Appreciate itFrancescoIl giorno ven 27 ott 2023 alle ore 16:37 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:Then, https://github.com/OCA/purchase-workflow/tree/16.0/purchase_partner_selectable_option, but I prefer to avoid that option.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
----
by Francesco Foresti - 12:48 - 30 Oct 2023 -
Re: Looking for purchase module to filter vendors in PO
Thanks, that's a good starting point!Appreciate itFrancescoIl giorno ven 27 ott 2023 alle ore 16:37 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:Then, https://github.com/OCA/purchase-workflow/tree/16.0/purchase_partner_selectable_option, but I prefer to avoid that option.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Francesco Foresti - 04:47 - 27 Oct 2023 -
Re: Looking for purchase module to filter vendors in PO
Then, https://github.com/OCA/purchase-workflow/tree/16.0/purchase_partner_selectable_option, but I prefer to avoid that option.Regards.
by Pedro M. Baeza - 04:36 - 27 Oct 2023 -
Re: Looking for purchase module to filter vendors in PO
Thanks Pedro,we already use this one and it's very useful, but the issue here is in partner selection, not product.How do I restrict field to not have Employees, Customers, random partners appearing?CheersFrancescoIl giorno ven 27 ott 2023 alle ore 16:17 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Francesco Foresti - 04:27 - 27 Oct 2023 -
-
-
EAN 13 pattern with barcodes_generator_product
Hi,I'm trying to use https://github.com/OCA/stock-logistics-barcode/tree/14.0/barcodes_generator_product to generate barcodes using GS1 barcodes purchased by customer.I see in the readme the example:For example, a typical pattern for products is "20.....{NNNDD}" that means that: * the EAN13 code will begin by '20' * followed by 5 digits (named Barcode Base in this module) * and after 5 others digits to define the variable price * a 13 digit controlThe pattern I'd like to implement is 8069235 + 5 digits provided by barcode base + 1 check digit.How does this translate in the format from the example ("20.....{NNNDD}")? Does any one have any reference guide for this?Thanks!
by Francesco Foresti - 06:36 - 25 Oct 2023-
Re: EAN 13 pattern with barcodes_generator_product
Thanks David, this works!I'll add that to module documentation.Cheers!Il giorno mer 25 ott 2023 alle ore 18:52 David Vidal <notifications@odoo-community.org> ha scritto:You don't really need the variable stuff (which is a bit misleading IMO). You should be fine with a pattern like "8069235....." your merchant code + 5 secuential digits (the control digit is generated automatically by the EAN13 rule)El mié, 25 oct 2023 a las 18:36, Francesco Foresti (<notifications@odoo-community.org>) escribió:Hi,I'm trying to use https://github.com/OCA/stock-logistics-barcode/tree/14.0/barcodes_generator_product to generate barcodes using GS1 barcodes purchased by customer.I see in the readme the example:For example, a typical pattern for products is "20.....{NNNDD}" that means that: * the EAN13 code will begin by '20' * followed by 5 digits (named Barcode Base in this module) * and after 5 others digits to define the variable price * a 13 digit controlThe pattern I'd like to implement is 8069235 + 5 digits provided by barcode base + 1 check digit.How does this translate in the format from the example ("20.....{NNNDD}")? Does any one have any reference guide for this?Thanks!
_______________________________________________
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 Francesco Foresti - 07:01 - 25 Oct 2023 -
Re: EAN 13 pattern with barcodes_generator_product
You don't really need the variable stuff (which is a bit misleading IMO). You should be fine with a pattern like "8069235....." your merchant code + 5 secuential digits (the control digit is generated automatically by the EAN13 rule)El mié, 25 oct 2023 a las 18:36, Francesco Foresti (<notifications@odoo-community.org>) escribió:Hi,I'm trying to use https://github.com/OCA/stock-logistics-barcode/tree/14.0/barcodes_generator_product to generate barcodes using GS1 barcodes purchased by customer.I see in the readme the example:For example, a typical pattern for products is "20.....{NNNDD}" that means that: * the EAN13 code will begin by '20' * followed by 5 digits (named Barcode Base in this module) * and after 5 others digits to define the variable price * a 13 digit controlThe pattern I'd like to implement is 8069235 + 5 digits provided by barcode base + 1 check digit.How does this translate in the format from the example ("20.....{NNNDD}")? Does any one have any reference guide for this?Thanks!_______________________________________________
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 Vidal - 06:50 - 25 Oct 2023
-
