PYTHONBREAKPOINT should ignore non-importable breakpoints

Feature or enhancement

Proposal:

I'd like to use ipdb rather than the built-in pdb by default for my breakpoints. However, if I set PYTHONBREAKPOINT="ipdb.set_trace" as a global shell environment variable, and the project does not have ipdb available, then all breakpoints are disabled:

/Users/tomforbes/.../cli.py:144: RuntimeWarning: Ignoring unimportable $PYTHONBREAKPOINT: "ipdb.set_trace"
  breakpoint()

IMO this isn't very user-friendly and can be quite annoying: I need to remember to export it on a per-project or per-shell basis. It would be great to fall back to the standard pdb breakpoint handler if the import fails.

If this is a compatability issue, perhaps a new PYTHONDEFAULTBREAKPOINT env variable could be added (and that can be set globally), which is used if available and falls back to pdb if not?

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Inizia tracciando come viene gestito PYTHONBREAKPOINT quando viene chiamato breakpoint(), incluso il RuntimeWarning esistente per un handler non importabile. Definisci il comportamento di fallback per ipdb.set_trace non disponibile, mantenendo l’handler standard pdb, e aggiungi la copertura per gli handler di breakpoint sia importabili sia non disponibili.