TGTGInsighttelegram intelligenceLIVE / telegram public index
← Python Заметки

TGINSIGHT SIMILAR POSTS

Најди сличен содржај

Изворен канал @pythonotes · Post #60 · 31 мар.

Вторая по частоте future-функция, которую я использовал, это абсолютный импорт from __future__ import absolute_import Что она делает? Изменения, которые вносит эта инъекция описаны в PEP328 Покажу простой пример. Допустим, есть такой пакет: /my_package /__init__.py /main.py /string.py Смотрим код в my_package/main.py # main.py import string Простой пример готов) Вопрос в том, какой модуль импортируется в данном случае? Есть два варианта: 1. модуль в моём пакете my_package.string 2. стандартный модуль string И вот тут вступает в дело приоритет импортов. В Python2 порядок следующий: помимо иных источников, раньше ищется модуль внутри текущего пакета, а потом в стандартных библиотеках. Таким образом мы импортнём my_package.string. Но в Python3 это поведение изменилось. Если мы указываем просто имя пакета, то ищется именно такой модуль, игнорируя имена в текущем пакете. Если мы хотим импортнуть именно подмодуль из нашего пакета то, мы должны теперь явно это указывать. from my_package import string или относительный импорт, но с указанием пути относительно текущего модуля main from . import string Еще одной неоднозначностью меньше 😎 Подробней про импорты здесь: https://docs.python.org/3/tutorial/modules.html #2to3#pep#basic

Резултати

Пронајдени 4 слични објави

Пребарај: #oauth2

当前筛选 #oauth2清除筛选
GitHub Trends

@githubtrending · Post #14663 · 02.05.2025 г., 12:30

#python#agents#ai#ai_agents#api#developer_tools#function_calling#integration#llm#mcp#oauth2#open_source#permissions#tools ACI.dev is an open-source platform that helps build AI agents by providing easy access to over 600 tools. It simplifies authentication and tool integration, allowing AI agents to work with many services like Google Calendar and Slack without needing separate setups. This platform offers multi-tenant authentication, flexible access methods, and natural language permissions, making it easier to manage and secure AI agent capabilities. It's open-source and works with any framework, which means you can build AI agents without worrying about vendor lock-in. https://github.com/aipotheosis-labs/aci

GitHub Trends

@githubtrending · Post #15214 · 12.10.2025 г., 11:30

#python#agents#ai#ai_agents#api#developer_tools#discord#function_calling#integration#llm#mcp#mcp_client#mcp_server#oauth2#open_source Klavis AI helps developers connect AI tools to other services like GitHub, Gmail, and Slack easily. It offers hosted servers that handle authentication and client code automatically, making it simpler to integrate AI with various platforms. This saves time and effort by eliminating the need for custom authentication management and client library maintenance. Users can quickly set up and scale their AI applications without worrying about complex integrations, making it easier to deploy AI-powered workflows securely and efficiently. https://github.com/Klavis-AI/klavis

GitHub Trends

@githubtrending · Post #15556 · 12.03.2026 г., 12:30

#typescript#ai#ai_agents#coding#deno#embeddings#insforge#nextjs#oauth2#pgvector#postgresql#realtime#vectors#websockets InsForge is an open-source backend platform for AI coding agents, offering easy auth, Postgres database, S3 storage, edge functions, and model gateway via a simple semantic layer. Agents fetch context, configure services, and inspect state to build full-stack apps quickly. Set up locally with Docker or use cloud deploys. It boosts agent accuracy 1.7x, speed 1.6x, and cuts tokens 30% vs. rivals, letting you prototype and ship AI-driven apps faster with less hassle and cost. https://github.com/InsForge/InsForge

GitHub Trends

@githubtrending · Post #14691 · 10.05.2025 г., 00:00

#csharp#architecture#aspnetcore#clean_architecture#cqrs#ddd#dotnet#dotnetcore#event_driven_architecture#event_sourcing#kubernetes#masstransit#messaging#microservice#microservices#oauth2#opentelemetry#software_architecture#software_design#software_engineering#vertical_slice_architecture Migrating from a monolithic architecture to a cloud-native microservices architecture offers several benefits. It improves scalability, allowing different parts of the application to grow independently. This approach also enhances reliability by isolating faults, so if one service fails, others continue to work. Additionally, microservices enable faster deployment and updates, as each service can be developed and deployed separately. This flexibility allows teams to use the best technology for each service, making development more efficient and agile[2][3][5]. https://github.com/meysamhadeli/monolith-to-cloud-architecture