Hello,
Good job, it is a great improvement, that will offer a lot of possibility.
But I'm not sure that doing now major API modifications will really fit the release cycle. I am wondering if these changes have their place in 6.0.x series even in 6.x.x series.
OpenERP v6 it starting is true stabilization step. I'm not sure that it is the appropriated moment to ask community to do more effort to stabilize addons/custom code du to major changes now.
It is true that these changes are welcome but minor changes should follow minor release and major changes should follow major release.
these changes also give modification and new way of managing ERP server, deamons etc. Such modification should be planned and announce at lesat 2 or three month in advance.
Something that is too volatile is not good for business even if all improvement are welcome.
Regards
Nicolas
Le 8 févr. 2011 à 16:16, Vo Minh Thu a écrit :
Hi,
Now that the release of the 6.0 version of OpenERP is done, we are happy
to have the opportunity to tackle something we wanted to do for some
time: make the server code available as an 'openerp' python module.
The necessary changes should be done in 'trunk' by the time you receive
this message. To retain backward compatibility, all the available
symbols under openerp will still be available without the 'openerp.'
prefix. All current addons should work unchanged but you can start to
use the new 'openerp.' hierarchy now.
This move is just a start and we want to bring more improvements. In
particular, we plan to reorganize the content of some modules,
especially 'openerp.tools'.
Note that now the bin/openerp-server.py script is moved at the root of
the project. A wrapper is available in bin/ if you need it.
To demonstrate the use of the openerp module, here is a little script.
You can try it without any OpenERP server running and it will set any
non-'active' user to 'active' in the 'test' database. We plan to provide
a better API in the future. The appropriate use of try/except/finally
should be added to any real code using cr.
import openerp
openerp.tools.config['addons_path'] = '/home/openerp/repo/addons/'
db, pool = openerp.pooler.get_db_and_pool('test')
cr = db.cursor()
res_users = pool.get('res.users')
ids = res_users.search(cr, 1, [('active', '=', False)])
for record in res_users.browse(cr, 1, ids):
print record.name
res_users.write(cr, 1, [record.id], {'active': True})
cr.commit()
cr.close()
Any feedback/comments welcome!
Thu
(On behalf of the R&D team)
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
--------------------------------------------------------------------
Nicolas Bessi
Senior ERP consultant
Business Solution technical leader
Camptocamp SA
PSE A
CH-1015 Lausanne
http://www.openerp.camptocamp.com
Phone: +41 21 619 10 26
Office: +41 21 619 10 10
Fax : +41 21 619 10 00
--------------------------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
