Note that there are some explanatory texts on larger screens.

plurals
  1. POOpenERP & Python Tools for Visual Studio compile error
    text
    copied!<p>I'm trying to get the OpenERP server to build and run in Visual Studio 2012 using Python Tools for Visual Studio.</p> <p>At the moment I get more than 2300 error messages, mostly along the lines of:</p> <pre><code>unexpected token 'x1' </code></pre> <p>I've downloaded the openerp-server-6.0.4 source and created a new Python project from Existing Python Code project in VS. I've selected the path to the OpenERP source(C:\OpenERP\Bin) when prompted and the file to execute when F5 is pressed is openerp-server.py. I've selected the Python 64-bit 3.3 interpreter.</p> <p>The project is created, but even before building I receive the numerous unexpected token errors. For example in the account.py file it complain about an unexpected token 'tax' in the following code:</p> <pre><code> tax.type=='code': address = address_id and obj_partener_address.browse(cr, uid, address_id) or None localdict = {'price_unit':cur_price_unit, 'address':address, 'product':product, 'partner':partner} exec tax.python_compute in localdict amount = localdict['result'] data['amount'] = amount </code></pre> <p>When using TOOLS > Python Tools > Execute Project in Python Interactive I see the following result:</p> <p>Python interactive window. Type $help for a list of commands.</p> <p>Resetting execution engine</p> <p>Interactive window is not yet started.</p> <p>Running C:\temp\openerp-server-6.0.4\bin\openerp-server.py</p> <p>Traceback (most recent call last):</p> <p>File "C:\temp\openerp-server-6.0.4\bin\openerp-server.py", line 64, in import tools</p> <p>File "C:\temp\openerp-server-6.0.4\bin\tools__init__.py", line 23, in import win32</p> <p>ImportError: No module named 'win32'</p> <p>Can anyone guide me into getting OpenERP to build and run using VS? Is it even possible?</p> <p>Thank you!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload