![trunk/5d6292dfff853cd0559300c88d7330752c185e40: [Native DSL] Add torch.backends.python_native (#178902)](https://avatars.githubusercontent.com/u/4992598?s=60&v=4)
trunk/5d6292dfff853cd0559300c88d7330752c185e40: [Native DSL] Add torch.backends.python_native (#178902)
Summary: Adds user-facing control of python_native op overrides defined in torch._native . Allows for: Per-DSL control and information via. torch.backends.python_native.$dsl .name # (property) .available # (property) .enabled # (property, settable) .version # (property) .disable() # (method) .enable() # (method) .disabled() # (context manager) And module-level control via. torch.backends.python_native .available_dsls (property) .all_dsls (property) .get_dsl_operations() (method) .disable_operations() (method) .enable_operations() (method) .disable_dispatch_keys() (method) .enable_dispatch_keys() (method) .operations_disabled() (context) .operations_disabled() (context manager) Tests and docs for this functionality are also added. Test Plan: pytest -sv test/python_native/test_torch_backends
Summary:
Adds user-facing control of python_native op overrides defined in
torch._native. Allows for:_
Per-DSL control and information via.
torch.backends.python_native.$dsl
.name # (property)
.available # (property)
.enabled # (property, settable)
.version # (property)
.disable() # (method)
.enable() # (method)
.disabled() # (context manager)
torch.backends.python_native.$dsl
.name # (property)
.available # (property)
.enabled # (property, settable)
.version # (property)
.disable() # (method)
.enable() # (method)
.disabled() # (context manager)
And module-level control via.
torch.backends.python_native
.available_dsls (property)
.all_dsls (property)
.get_dsl_operations() (method)
.disable_operations() (method)
.enable_operations() (method)
.disable_dispatch_keys() (method)
.enable_dispatch_keys() (method)
.operations_disabled() (context)
.operations_disabled() (context manager)
torch.backends.python_native
.available_dsls (property)
.all_dsls (property)
.get_dsl_operations() (method)
.disable_operations() (method)
.enable_operations() (method)
.disable_dispatch_keys() (method)
.enable_dispatch_keys() (method)
.operations_disabled() (context)
.operations_disabled() (context manager)
Tests and docs for this functionality are also added.
Test Plan:
pytest -sv test/python_native/test_torch_backends.py
pytest -sv test/python_native/test_torch_backends.py
Signed-off-by: Simon Layton
Pull Request resolved: https://github.com/pytorch/pytorch/pull/178902 Approved by: https://github.com/albanD`
Assets 2
PyTorch Releases
https://github.com/pytorch/pytorch/releases/tag/trunk%2F5d6292dfff853cd0559300c88d7330752c185e40Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
availableversiongithub
5 Patterns for Building Resilient Event-Driven Integrations
Point-to-point integrations are easy to build and easy to break. You wire up an API call from one system to another, it works in testing, and then a 30-second downstream outage in production causes a cascade of failures, lost state, and a manual cleanup effort that takes longer than the outage itself. Event-driven integration patterns address this directly. They decouple the systems involved so that no single failure propagates through the entire integration chain. The tradeoff is upfront design work, but the operational stability that results is not comparable to the alternative. Here are five patterns that appear in most well-built event-driven integrations, with examples of when and why each one matters. 1. Queue-Based Event Processing What it is: Instead of processing webhook events or
🚀 Build a Professional Image Converter GUI in Python (Step-by-Step)
👉 Full source code: https://github.com/rogers-cyber/python-tiny-tools/blob/main/63-Image-resizer/ImageConvertPRO.py 🧠 What You’ll Build In this tutorial, we’ll create a modern desktop app that can: 📂 Add images (files, folders, drag drop) 🖼 Preview thumbnails 🔄 Convert formats (PNG, JPEG, WEBP, etc.) 📏 Resize images 💾 Save conversion history (SQLite) ⚡ Run conversions in background (no freezing UI) 📦 Step 1: Install Dependencies pip install pillow ttkbootstrap tkinterdnd2 🔍 Why we need them: Pillow → image processing ttkbootstrap → modern UI styling tkinterdnd2 → drag drop support 📁 Step 2: Project Setup Create a Python file: image_convert_pro.py ⚙️ Step 3: Import Libraries import os import sys import sqlite3 from threading import Thread from PIL import Image , ImageTk 🧠 Explana
Claude Code Hooks: How to Auto-Format, Lint, and Test on Every Save
Configure hooks in .claude/settings.json to run prettier, eslint, and tests automatically, ensuring clean code without manual intervention. Claude Code Hooks: How to Auto-Format, Lint, and Test on Every Save Claude Code hooks are your automation layer for agentic development. They let you run shell commands at specific points in Claude's workflow—before tools run, after files are written, or when sessions end. Most developers discover hooks when they're tired of Claude writing code that doesn't match their formatter settings. Here's how to stop that permanently. Where Hooks Live Hooks go in your CLAUDE.md or in .claude/settings.json at the project root: { "hooks" : { "afterFileWrite" : "prettier --write $FILE" , "afterSessionEnd" : "npm test -- --passWithNoTests" } } The $FILE variable con
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Releases
I Turned My MacBook's Notch Into a Control Center for AI Coding Agents
Every developer using Claude Code knows the pain: you have 5+ terminal sessions running, Claude is asking for permission in one tab, waiting for input in another, and you're buried in a third. You Alt-Tab frantically, lose context, and waste time. So I built CodeIsland — a free, open-source macOS app that turns your MacBook's notch (Dynamic Island) into a real-time dashboard for all your AI coding agents. The Problem When you're running multiple Claude Code sessions across different projects, there's no way to see everything at a glance. You're constantly switching between terminals to: Check which session finished Approve permission requests Answer Claude's questions Monitor usage limits Multiple Claude Code sessions in cmux, with CodeIsland monitoring everything from the notch The Soluti
BuildWithAI: What Broke, What I Learned, What's Next
Overview The architecture and the prompts are covered. Now for the part that usually gets left out: what actually broke, what could be better, and how to deploy the whole thing on your own AWS account. So far we've gone through the serverless stack and 5-layer cost guardrails, then the system prompt pattern and the prompt engineering behind all six tools. This final part is the practical side — the gotchas from development and a step-by-step guide so you can fork the repo and get it running yourself. Things that broke Bedrock model access First deploy went fine. Lambda functions created, API Gateway live, DynamoDB provisioned. Then the first endpoint returned access denied from Bedrock. No helpful error message, just a generic denial. The issue: when I first deployed this using Claude Sonn
BuildWithAI: Architecting a Serverless DR Toolkit on AWS
Overview I'd been getting more involved in disaster recovery planning lately and kept running into the same gap — a lot of teams on AWS have backups, but not a real Disaster Recovery (DR) plan. No documented runbooks, no tested failover procedures, no RTO/RPO targets tied to business impact. So that became the motivation for this side project: six AI-powered tools that automate the tedious parts of DR planning, built entirely on AWS. In part one of this three-part series, we will walk through the architecture — the serverless stack, the central model config, and the 5-layer cost guardrail system that keeps everything under $10/month (of course, you can set your own threshold; that's just what felt right for this side project). The next two parts will cover prompt engineering for each tool
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!