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

WTForms is a flexible forms validation and rendering library for Python web development. It can work with whatever web framework and template engine you choose. It supports data validation, CSRF protection, internationalization (I18N), and more. There are various community libraries that provide closer integration with popular frameworks. WTForms tries to provide as usable an API as possible. We’ve listed here some of the known libraries to work with WTForms, but if it’s not listed, it doesn’t mean it won’t work. Pretty much any ORM or object-DB should work, as long as data objects allow attribute access to their members. WTForms uses unicode strings throughout the source code and assumes that form input has already been coerced to unicode by your framework. WTForms fields render to unicode strings by default, and therefore as long as your templating engine can work with that, you should have no unicode issues.

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.