Re: [pyxser-users] Pyxser generates strange 'name' attribute values
Brought to you by:
damowe
From: Daniel M. W. <dm...@co...> - 2010-05-10 14:24:06
|
On Friday 07 May 2010, Max Sinelnikov <ms...@gm...> wrote: > Oh, sorry, I clicked 'Reply' instead of 'Reply to all' and forgot to > attache files. NP Max, I think that the problem is solved, please try the r145 on trunk. Please notify me if that works, I've made some small test here, but I need to be sure that it works with your application :) Thanks in advance... > Original message: > > > Hi, Daniel. > > > Thanks for your feedback. The code is fixed, pyxser now supports > > > > unicode keys on dictionaries. I've refactored the code, so pyxser > > now runs faster. I want to release pyxser-1.4.4r tomorrow, so if can > > have your feedback about how is working the trunk branch of it, it > > would be very helpful, since I don't have access to the modules > > that you are using... > > I'm happy with revision 143. All my objects successfully serialized(I > don't need for deserializing now, so I haven't test this functionality > yet, sorry-)) > But there is the same problem when I'm serializing one of my objects > with depth=12 and more. I attached two files to this mail: > depth-11.xml is a valid xml document I got with depth=11, and > depth-12.xml is the same serialized object with depth=12. Problem is > with Resource object objid="id33427536"(depth-12.xml, Line 58). > > A few words about objects I have. I'm using sqlalchemy on top of > mysql, there are several tables with relations. SQLAlchemy creates > objects related to tables and, for exapmle, I have object named > "company" with attribute "roles" which looks like list. Every item of > company.roles is an company_role instance and so on. It's possible to > > do something like this(as example): > >>> r = Resource.get_by_id(1) > >>> company.roles[1].permissions[0].pack.resources[0] is r > > True > > I'm trying to reproduce described issue with simple schema, but with > no success. I thoungth that there may be a problem with nested > dictionries, but things like t.a = > {'hehe':{'ololo':{'haha':{u'хехе':{u'наан':{u'чочо':{u'хрхрх':11}}}}}}} > works fine. Will try again during this holidays. > > Best regards, Max Sinelnikov. Best regards, -- Daniel Molina Wegener <dmw [at] coder [dot] cl> Software Architect, System Programmer & Web Developer Phone: +56 (2) 979-0277 | Blog: http://coder.cl/ |