Bug report
Bug description:
Using specific values as variable names in breakpoints leads to incorrect behaviour.
This seems to be because certain chars are used as aliases in pdb, i.e c is continue, p is print etc.
It is triggered when the following char is non-alpha-numeric, afaict.
MRE:
Python 3.9.5 (default, Sep 14 2021, 12:04:19)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> breakpoint()
--Return--
> <stdin>(1)<module>()->None
(Pdb) c = None
>>> c
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'c' is not defined
>>>
# I expect to still be in a breakpoint here, and for `c` to be `None`, but pdb has 'continued' execution instead.
The same is true for other aliases, like q and p, which raise errors relating to their respective functions. (I have not tried all aliases).
CPython versions tested on:
3.9
Operating systems tested on:
Linux
Bug report
Bug description:
Using specific values as variable names in breakpoints leads to incorrect behaviour.
This seems to be because certain chars are used as aliases in pdb, i.e
ciscontinue,pisprintetc.It is triggered when the following char is non-alpha-numeric, afaict.
MRE:
The same is true for other aliases, like
qandp, which raise errors relating to their respective functions. (I have not tried all aliases).CPython versions tested on:
3.9
Operating systems tested on:
Linux