python-sql vs. regon vs. scrapestack vs. zope.interface Comparison Chart

litex.regon, a frontend for Polish REGON database. Simple, pythonic wrapper for REGON database. To access its SOAP API, one needs a user key issued by REGON administrators. REGONAPI accepts one argument, the service URL (provided by REGON administrators). After login, one can start querying the database. Single REGON number (either 9 or 14 digits long), single 10 digit KRS number, single NIP (10 digits strings), collection of REGONs (all of them have to be either 14 or 9 digits long), collection of KRSs, collection of NIPs. Only one parameter is used in the query. If multiple ones are passed, first from the above list is taken into account. Additionally, a detailed parameter can be passed, detailed=True causes the search method to fetch the default detailed report. If one knows the REGON of a business entity and a detailed report name, a full report can be fetched directly.

This package is intended to be independently reusable in any Python project. It is maintained by the Zope Toolkit project. This package provides an implementation of “object interfaces” for Python. Interfaces are a mechanism for labeling objects as conforming to a given API or contract. So, this package can be considered as an implementation of the Design By Contract methodology support in Python. Interfaces are objects that specify (document) the external behavior of objects that “provide” them. An interface specifies behavior through informal documentation in a doc string, attribute definitions, and invariants, which are conditions that must hold for objects that provide the interface. Attribute definitions specify specific attributes. They define the attribute name and provide documentation and constraints of attribute values. Attribute definitions can take a number of forms.