Tuesday, November 15, 2016
2 changes · master
Enhancements to existing features
The startup script now explicitly uses the correct Python version instead of relying on the system default. This helps Odoo run consistently on distributions where the generic Python command points to a different version, reducing setup work for users.
Original PR description
Description of the issue/feature this PR addresses: This PR is an attempt to make Odoo adhere to [PEP 394](https://www.python.org/dev/peps/pep-0394/) Quoting the PEP > In order to tolerate…
Description of the issue/feature this PR addresses: This PR is an attempt to make Odoo adhere to [PEP 394](https://www.python.org/dev/peps/pep-0394/) Quoting the PEP > In order to tolerate differences across platforms, all new code that needs to invoke the Python interpreter should not specify python , but rather should specify either python2 or python3 (or the more specific python2.x and python3.x versions; Current behavior before PR: On distros that have python mapped to python3, Odoo uses python3 instead of python2 when the odoo-bin script is run In previous versions of Odoo it was easy to get around this by directly specifying using python2 to run odoo.py like this `python2` odoo.py With the new `odoo-bin` script the only way to get this to work without modifying the script is to map python to python2 (Which would break other python programs on the machine) or create a `virtual-env` where python refers to python2. Desired behavior after PR is merged: odoo-bin works properly regardless of the distro it's run on Users don't have to create an alias or create a `virtual-env` to run odoo if they don't want to. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr On distros that have python mapped to python3 Odoo uses python3 instead of python2 when the odoo-bin script is run
Sales orders paid immediately now use an already-paid payment term instead of showing a future due date. This keeps invoices clearer for customers and avoids confusion when payment has already been completed.
Original PR description
Before this commit, your SO was automatically confirmed when using an instant payment provider, but the payment term was not updated accordingly, resulting in confusing invoices that were already paid but still showed a payment term in the future.