Thou I suppose this is more of a feature suggestion than a bug, but it would be nice to have 3 levels (instead of 2) of variable visibility -- First level would be what was originally shown before the fix, 2nd what is shown now before pressing *, 3rd after pressing * -- Great that all variables are shown thou it gets a bit clustered
On Tue, Jan 1, 2013 at 1:17 PM, asaf ebgi <[email protected]> wrote: > Hi thanks for the reply and sorry for the belated response -- Yes that > fixed the issue -- Thanks > > On Tue, Aug 14, 2012 at 8:25 PM, Andreas Kloeckner > <[email protected]> wrote: >> asaf ebgi <[email protected]> writes: >> >>> Well, I am actually inspecting code from the tastypie django library - >>> -So there is lots of code --But an example is below: >>> In the Variables List: >>> >>> Variables: >>> instance: User >>> self: ForeignRelatedObjectsDescriptor >>> | .related: RelatedObject >>> superclass: <class 'django.db.models.manager.Manager'> >>> >>> (self is expanded) >>> >>> in the console I type: >>> >>>>>> dir(self) >>> ['__class__', '__delattr__', '__dict__', '__doc__', '__format__', >>> '__get__', '__getattribute__', '__hash__', '__init__', '__module__', >>> '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__set__', >>> '__setattr__', '__sizeof__', '__str__', '__subclasshook__', >>> '__weakref__', 'create_manager', 'delete_manager', 'related'] >>> >>>>>> getattr(self, 'related') >>> <RelatedObject: app:profile related to user> >>> ('related' appears in the Variables list) >>> >>>>>> getattr(self, 'delete_manager') >>> <bound method ForeignRelatedObjectsDescriptor.delete_manager of >>> <django.db.models.fields.related.ForeignRelatedObjectsDescriptor >>> object at 0x1bdaed0>> >>> ('delete_manager' does not appear in Variables list -- Neither does >>> create_manager) >> >> Can you try and see if this is fixed in git? >> >> Thanks, >> Andreas _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
