Click-odoo

Latest version: v1.6.0

Safety actively analyzes 629811 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 4

1.0.2

------------------
- refactor the OdooEnvironment class: it is much cleaner when
it leaves the global Odoo config alone, so we completely move
responsibility to initialize the Odoo config to the CLI part.

1.0.1

------------------
- better error logging and handling: all exceptions occuring
in scripts under click_odoo.env_options are logged and converted
to ClickException so we are sure they are both in the log file
and on the console (handled by click) for the user to see.
The OdooEnvironment context manager does not do additional logging,
leaving that responsibility to the caller.

1.0.0

------------------
- close db connections when releasing OdooEnvironment
- expose click_odoo.odoo_bin (odoo or openerp-server depending on Odoo series).
not documented yet, because it should ideally be a full path corresponding
to the installed click_odoo.odoo, and I'm not sure how best to detect it yet.

1.0.0b4

--------------------
- minor documentation improvements
- add the possibility to run script without ``--database`` (ie without env,
but with a properly initialized Odoo library such as addons path)
- be more resilient in case we can't obtain a context for the user

1.0.0b3

--------------------
- click_odoo now exports the odoo namespace: ``from click_odoo import odoo``
is an alias for ``import odoo`` (>9) or ``import openerp as odoo`` (<=9)
- add a ``with_rollback`` option to the ``env_options`` decorator, to control
the presence of the rollback option
- document the ``env_options`` decorator

1.0.0b2

--------------------
- commit in case of success, so users do not need to commit in their
scripts, therefore making scripts easier to compose in larger transactions
- add a --rollback option
- interactive mode forces --rollback

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.