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

Изворен канал @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

Hashtags

#pydantic #libs

Резултати

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

Пребарај: #ethanalysis

当前筛选 #ethanalysis清除筛选

The Kingfisher - Bitcoin & Crypto liquidations signals and analytics

@thekingfisher_btc · Post #3875 · 12.02.2025 г., 13:44

Најди слично Погледај

Okay, here's an analysis of the ETH liquidation map suitable for Twitter, formatted in Markdown: 🚨#ETH Liquidation Map Analysis 🚨 Here's what the liquidation map tells us about potential price action. 👇 1️⃣Main Liquidation Zones: The BIGGEST liquidation cluster is concentrated AROUND & BELOW the current price (~$2626). Smaller clusters exist further below, around the 2500 to 2600 levels, while Long liquidations reside further above, between 2690 and 2712. 2️⃣Key Price Levels to Watch: * Potential Support (Liquidation Zone): $2500-$2600 acts as strong support and bounce zone. * Danger zone: 2626, current price is the biggest Liquidation cluster * Resistance (Liquidation Zone): $2690 - $2712; push beyond here could trigger more long liquidations. 3️⃣Longs vs. Shorts: The image shows FAR more long liquidations than short liquidations which have already been cleared out. A HUGE cluster of longs is currently sitting under the current price, which can be liquidated. 4️⃣Potential Price Movements: Given the concentration of long liquidations below the current price, a move *DOWN* to trigger those liquidations seems more probable. 📉 Expect volatility around these liquidation zones! 5️⃣Key Takeaways for Traders: * Be cautious of longing: Lots of longs sitting right at the current price could be liquidated. * Anticipate volatility: Large liquidations can fuel price swings. Manage your risk accordingly! * Watch key levels: $2500-$2600 as a potential support/bounce area and $2690-$2712 as potential resistance. Disclaimer: This is just an analysis of liquidation data and not financial advice. Trade responsibly! #Crypto#Trading#Liquidations#ETHanalysis📊

Hashtags

#eth #crypto #trading #liquidations #ethanalysis