# Decoupling python workflow from c++ core

**URL:** <https://dev-discuss.pytorch.org/t/decoupling-python-workflow-from-c-core/3462>\
**Category:** Uncategorized\
**Created:** [October 6, 2026, 3:59am UTC](https://dev-discuss.pytorch.org/t/decoupling-python-workflow-from-c-core/3462 "2026-10-06T03:59:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtk2xfugaku](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/mtk2xfugaku/32/2136_2.png) [@mtk2xfugaku](https://dev-discuss.pytorch.org/u/mtk2xfugaku)\
**Post date:** [October 6, 2026, 3:59am UTC](https://dev-discuss.pytorch.org/t/decoupling-python-workflow-from-c-core/3462/1 "2026-10-06T03:59:49Z")

</div>

I was wondering if it would make sense to decouple pytorch’s python frontend and C++ core in the same way like jax and jaxlib. Since most of the Pytorch 2.0 development is focused around python (Dynamo’s symbolic interpreter, fx tracing and pattern matching, and inductor) it would be easier to focus on python side of the development without building C++ heavy core, aten and c10 libraries just for python development.

---

<div class="post-metadata">

**Author:** ![albanD](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/alband/32/9_2.png) [@albanD](https://dev-discuss.pytorch.org/u/albanD)\
**Post date:** [October 7, 2026, 5:06pm UTC](https://dev-discuss.pytorch.org/t/decoupling-python-workflow-from-c-core/3462/2 "2026-10-07T17:06:02Z")

</div>

Thanks for the suggestion.

I don’t think there is any plan to go towards that today no. Even the new pt2 stack relies very heavily on C++ code and components to achieve the appropriate speed.