Telerik DevCraft
Get 1,250+ .NET and JavaScript components for building feature-rich and professionally designed web, desktop, and mobile apps in less time and with fewer efforts. Plus, complete .NET embedded reporting. Standardize the look and feel of your applications across the board. Out-of-the-box themes and limitless customization options allow you to quickly present a professional, well-packed frontend to your users. Simplify your everyday software development tasks. Cut down with up to 50% development time, increase productivity, and follow the latest technology and user experience trends. Review demos, tutorials, feature descriptions, code samples, and detailed APIs. Benefit from leading support even during your free trial, extensive documentation, and community forums. Enjoy the finest and most complete software development tooling collection with .NET and JavaScript UI components for web, desktop, and mobile applications, reporting and report management solutions, automated testing, etc.
Learn more
waiting
waiting is a small library for waiting for stuff to happen. It basically waits for a function to return True, in various modes. Waiting is compatible with flux for simulated timelines. The most basic usage is when you have a function you want to wait for. Waiting forever is very simple. If your predicate returns a value, it will be returned as the result of wait(). A timeout parameter can also be specified. When a timeout expires without the predicate being fulfilled, an exception is thrown. Sleeping polls the predicate at a certain interval (by default 1 second). The interval can be changed with the sleep_seconds argument. When waiting for multiple predicates, waiting provides two simple facilities to help aggregate them, any and all. They resemble Python’s built-in any() and all(), except that they don’t call a predicate once it has been satisfied (this is useful when the predicates are inefficient and take time to complete).
Learn more
WTForms
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.
Learn more
yarl
All URL parts, scheme, user, password, host, port, path, query, and fragment are accessible by properties. All URL manipulations produce a new URL object. Strings passed to constructor and modification methods are automatically encoded giving canonical representation as result. Regular properties are percent-decoded, use raw_ versions for getting encoded strings. Human-readable representation of URL is available as .human_repr(). PyPI contains binary wheels for Linux, Windows and MacOS. If you want to install yarl on another operating system (like Alpine Linux, which is not manylinux-compliant because of the missing glibc and therefore, cannot be used with our wheels) the tarball will be used to compile the library from the source code. It requires a C compiler and Python headers installed. Please note that the pure-Python (uncompiled) version is much slower. However, PyPy always uses a pure-Python implementation, and, as such, it is unaffected by this variable.
Learn more