Migration scripts for purchase_payment v7 module
This module includes the needed migration script for making a smooth transition from v7 _purchase_payment_ (a complement of _account_payment_extension_ module) to the set of v8 bank-payment modules.
This module doesn’t provide any functionality at user level.
Installation
You need openupgradelib for using these scripts, that can be installed via pip. You need also to have accesible the repository bank-payment from https://github.com/OCA/bank-payment.
Usage
Update the modules and the conversion will be automatically done, and this module will be automatically uninstalled.
Credits
Contributors
Pedro M. Baeza <pedro.baeza@serviciosbaeza.com>
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit http://odoo-community.org.
Metadata
Release files for odoo8-addon-purchase-payment 8.0.1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo8_addon_purchase_payment-8.0.1.0.0-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_purchase_payment-8.0.1.0.0-py2-none-any.whl |
Release files / odoo8_addon_purchase_payment-8.0.1.0.0-py2-none-any.whl
| Download URL | odoo8_addon_purchase_payment-8.0.1.0.0-py2-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
a385e7c9b3501e3c2c6f2ddd3df84a9ad3e9123c149a8c6d3cbe73ee913de5b1
|
|
BLAKE2b-256 checksum How to use checksums |
24061dd8a94703719e6932513529243875f3cab58c2c1c624a2e2b634709ff01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo8-addon-purchase-payment 8.0.1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.