[6.1/7.0] possible error : TypeError: 'must be type, not browse_record'

Bug #1301458 reported by Romain Deheele - Camptocamp on 2014-04-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Carriers And Deliveries Management
Critical
Romain Deheele - Camptocamp

Bug Description

Hi,

In base_delivery_carrier_files_document, file carrier_file.py,
by coincidence, the class and a frequently used parameter are both named "carrier_file".
in l.61, the super method will take carrier_file parameter while it needs carrier_file, the class name.
It causes logically the error : TypeError: 'must be type, not browse_record'

Regards,

Romain

Related branches

Changed in carriers-deliveries:
status: New → Fix Committed
importance: Undecided → Critical
assignee: nobody → Romain Deheele - Camptocamp (romaindeheele)
Changed in carriers-deliveries:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers