Hi, I could see a point in overhauling the __openerp__ dictionary and the conventions for v7, perhaps we should start gathering more points which could use adjustment ?
I have just a small one i'd like to see which would be rather easy: the author field should be a list, this way the current pollution of the Authors in apps.openerp.com could be minimized and would still give credit to authors where it is due. Now on the openerp side the author field is read as a string, with 2 lines or so we could change that and check for a list instance and just do a ', '.join() call on the list if so. On subject of dependencies I agree listing dependencies and their required versions would be great, although it's something that could explode into some very big/scary/buggy code very quickly if not managed properly. Thus I'd like to stress the importance of not re-inventing the wheel. Indeed the infrastructure for python is already there so we should perhaps examine what possible downsides we could have from using these tools. -- Niels Huylebroeck Lead Architect -- Agaplan Tel. : +32 (0) 93 95 98 90 Web : http://www.agaplan.eu
_______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
