pymc-devs / pymc-devs/pytensor

Proposal: Make compiler optional and fall-back to numba or JAX

Open
#1,027 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backend compatibility C-backend installation needs info
Dominant language
Python
Stars
644
Forks
208
Avg merge
2d 14h
Merged PRs (30d)
16

Description

Description

Installing PyTensor with a full C++ compiler chain is very fragile and difficult to maintain. We have alternative backends that are much easier to maintain. While it seems we can't yet switch to them by default, how about:

  • We make a working c-compiler optional in the installation
  • If no working C-compiler is found, we fall back to use the JAX or numba backend.

That way, people that can't get their compilers installed, still get fast PyTensor.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the compiler-detection and backend-selection entry points, then determine how installation behaves without a working C++ compiler. Done means compiler installation is optional and PyTensor can fall back to the JAX or numba backend.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.