#python#agent#agentic#agentic_ai#agents#agents_sdk#ai#ai_agents#aiagentframework#genai#genai_chatbot#llm#llms#multi_agent#multi_agent_systems#multi_agents#multi_agents_collaboration
The Agent Development Kit (ADK) is an open-source Python toolkit that helps you easily build, test, and deploy smart AI agents, from simple helpers to complex multi-agent systems. It lets you write agent logic in Python, use many built-in or custom tools, and organize multiple agents to work together. You can deploy agents anywhere, including Google Cloud, and evaluate their performance with built-in tools. ADK supports flexible workflows and works with various AI models, not just Google’s. This means you get full control and flexibility to create powerful AI applications that fit your needs, speeding up development and making it easier to manage AI projects.
https://github.com/google/adk-python
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.