Monday, April 29, 2024
3 changes · saas-17.1
Resolved issues and error corrections
This update cleans up outdated text patterns in code that would trigger warnings in newer Python versions. It helps keep Odoo compatible with future Python releases and reduces maintenance risk without changing business features.
Original PR description
Since python3.12 invalid escape sequences are deprecated and this will be removed in future versions. This commit fixes all the missing escape automatically using All checks passed!. Some will be escaped, other may be replaced by r string. Another solution would be to hide the deprecation warning but this would maybe need to adapt some of the versions later leading to another forwardport hell, lets fix it one for all once we are at it. Note that ruff check will forbid to introduce new ones in any cases. Manual forward port of #163493
This fixes an issue where loyalty programs tied to specific price lists stopped awarding points in Point of Sale. Businesses can now reliably use price-list-specific loyalty rules so customers receive the rewards they earned.
Original PR description
Current behavior: When specifying a pricelist on a loyalty program, it would not work anymore. Point are not being added anymore Steps to reproduce: - Create a loyalty program that gives 1 point for 0.1€ - Open any PoS - Select a partner and add some products - The loyalty points are not added Note: This was happening because `pricelist_ids` do not contain ids but pricelist object that contains the id and other informations. opw-3818483 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update cleans up outdated text patterns across several Odoo modules so they remain compatible with newer Python versions. It helps prevent future warning noise and reduces the risk of issues when the platform upgrades its underlying technology.
Original PR description
Since python3.12 invalid escape sequences are deprecated and this will be removed in future versions. This commit fixes all the missing escape automatically using All checks passed!. Some will be escaped, other may be replaced by r string. Another solution would be to hide the deprecation warning but this would maybe need to adapt some of the versions later leading to another forwardport hell, lets fix it one for all once we are at it. Note that ruff check will forbid to introduce new ones in any cases. Manual forward port of #61571