Trunk: POS: local variable 'datetime' referenced before assignment
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Invalid
|
Undecided
|
Unassigned | |||
Odoo Server (MOVED TO GITHUB) | Status tracked in Trunk | |||||
Trunk |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi... I was testing new pos module on Trunk (downloaded last version from launchpad today 2010-02-13)
Bug 1: On second tab payment date is not filled even if payment has been done.
Bug 2: Reprint button gives me this one:
Environment Information :
System : Linux-2.
OS Name : posix
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty
Operating System Release : 2.6.28-11-generic
Operating System Version : #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
Operating System Architecture : 32bit
Operating System Locale : es_ES.UTF8
Python Version : 2.5.4
OpenERP-Client Version : 5.0.7
Last revision No. & ID :1139 <email address hidden>
Traceback (most recent call last):
File "/media/
(result, format) = obj.create(cr, uid, ids, datas, context)
File "/media/
fnct_ret = fnct(cr, uid, ids, data, report_xml, context)
File "/media/
return self.create_
File "/media/
pdf = create_
File "/media/
obj.render()
File "/media/
result = self._render()
File "/media/
return rml2pdf.
File "/media/
r.render(fp)
File "/media/
pt_
File "/media/
fis += r.render(
File "/media/
return process_
File "/media/
flow = self._flowable(
File "/media/
for i in self._textual(
File "/media/
rc1 = utils._
File "/media/
result += str(txt)
File "/media/
datetime = datetime.
UnboundLocalError: local variable 'datetime' referenced before assignment
Thank you!!
Related branches
Changed in openobject-server: | |
status: | New → Confirmed |
status: | Confirmed → Fix Released |
Re issue 2, looks like I missed it when I merged the mx.DateTime removal branch into trunk, sorry about that, it's fixed as of 2061 (revid:<email address hidden>)
By the way, next time would it be possible that you split the issues into separate bugs? They might come from the same source (haven't checked the first one), but if that's the case we can mark them as duplicates. On the other hand, putting several issues on a single report doesn't give us the same flexibility.
Thanks, and sorry about the breakage.