The python wrappers now reflect the Delphi inheritance hierarchy#399

pyscripter announced inAnnouncements

pyscripter

Dec 28, 2022

· 1 comments· 7 replies

Return to top

Discussion options

pyscripter
Dec 28, 2022
Maintainer

With the fix to#382, tp_base is correctly set for wrappers descending from TPyDelphiObject and registered through the standard RegisterDelphiWrapper mechanism. This means that the isinstance and issubclass builtins will work correctly on wrapped Delphi objects and classes.

It also means that we should not call inherited in RegisterMethods and RegisterGetSets, since python will find the inherited methods and getsets anyway. Calling inherited does not do any harm (it overrides the methods in inherited classes), but it is inefficient speed and memory-wise.

Wrapped classes which do not provide a RegisterMethods and RegisterGetSets override, they should provide an empty one. Otherwise the inherited ones would be created on both the parent and the child class leading to unnecessary duplication.

45ca26c removed the calls to inherited from existing implementations of RegisterMethods and RegisterGetSets. It also changed the implementation of the__dir__ wrapper. However, now, empty RegisterMethods and RegisterGetSets, should be added to the wrappers that do not have these methods.

@lmbelo,@jimmckeeth

You must be logged in to vote

Replies: 1 comment 7 replies

Comment options

lmbelo
Dec 28, 2022

We have this fixed and many other enhancements in the latest "docs" feature branch.

Have a look:https://github.com/Embarcadero/python4delphi/tree/docs

All methods and properties provided by Delphi are now built-in;
It follows the Delphi inheritance until Python object;
Python is now able to refer to class attributes;
The dir method now lists all Delphi attributes available in a class (not instances), categorized by class parents.
Callables are not created on-the-fly anymore;
Doc strings are being read from XML files;
IDE's can use type attributes as stubs for code completion, as they are built-in now;
and more...

@jimmckeeth @pyscripter

You must be logged in to vote

7 replies