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

TGINSIGHT SIMILAR POSTS

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

Изворен канал @pythonotes · Post #397 · 12 ное.

Использование Pydantic сегодня стало нормой, и это правильно. Но иногда на ревью вижу, что используют его не всегда корректно. Например, метод BaseModel.model_dump() по умолчанию не преобразует стандартные типы, такие как datetime, UUID или Decimal, в простой сериализуемый для JSON вид. Тогда пишут кастмоный сериализатор для этих типов чтобы функция json.dump() не падала с ошибкой. import uuid from datetime import datetime from decimal import Decimal from uuid import UUID from pydantic import BaseModel class MyModel(BaseModel): id: UUID date: datetime value: Decimal obj = MyModel( id=uuid.uuid4(), date=datetime.now(), value='1.23' ) print(obj.model_dump()) # не подходит для json.dump # { # 'id': UUID('4f8c1bc4-25fd-40cd-9dbe-2c73639b0dc1'), # 'date': datetime.datetime(2025, 12, 12, 12, 12, 12, 111111), # 'value': Decimal('1.23') # } # добавляем свой кастомный сериализатор json.dumps(obj.model_dump(), cls=MySerializer) # { # 'id': '4f8c1bc4-25fd-40cd-9dbe-2c73639b0dc1', # 'date': '2025-12-12T12:12:12.111111', # 'value': '1.23' # } В данном случае класс MySerializer обрабатывает datetime, UUID и Decimal. Например так: class MySerializer(json.JSONEncoder): def default(self, o): if isinstance(o, Decimal): return str(o) elif isinstance(o, datetime): return o.isoformat() elif isinstance(o, UUID): return str(o) return super().default(o) Специально для тех, кто всё еще так делает - в этом нет необходимости! Pydantic может это сделать сам, просто нужно добавить параметр mode="json". json.dumps(obj.model_dump(mode="json")) # { # 'id': '4f8c1bc4-25fd-40cd-9dbe-2c73639b0dc1', # 'date': '2012-12-12T12:12:12.111111', # 'value': '1.23' # } #pydantic#libs

Резултати

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

Пребарај: #samueldare

当前筛选 #samueldare清除筛选
Crypto M - Crypto News

@CryptoM · Post #65233 · 12.04.2026 г., 06:56

🚀 Bittensor Co-Founder Addresses Covenant AI Incident and Future Plans On April 12, Bittensor co-founder Jacob Robert Steeves responded to the Covenant AI incident, expressing his shock over recent developments. According to BlockBeats, Steeves accused Covenant AI founder Samuel Dare of actions that severely harmed the protocol and community, betraying the trust of investors and users. He apologized to those affected by the incident. Steeves stated that Bittensor was designed to combat greed and selfishness by enabling collective ownership of AI through a permissionless mechanism. He acknowledged that the incident exposed vulnerabilities in the system but also highlighted the opportunity to strengthen the protocol and community's resilience. Looking ahead, Steeves proposed advancing a "Locked Stake" mechanism, introducing a "time + stake" commitment dimension at the protocol level to enhance transparency and investor protection, thereby reducing similar risks. He noted that this plan was initially designed with Samuel Dare's involvement. Furthermore, Steeves mentioned that the development of subnets 3, 39, and 81 will continue under community leadership, with no changes to their overall functionality and vision. He emphasized that Bittensor remains one of the most decentralized AI protocols and will continue to promote open AI development, with plans to advance towards training larger-scale models, including a trillion-parameter model in the future. #Bittensor#CovenantAI#JacobRobertSteeves#SamuelDare#AI#Blockchain#DecentralizedAI#InvestorProtection#LockedStake#AIProtocol#CommunityLeadership#OpenAI#FuturePlans#TrillionParameterModel#TAO