Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Possibly, your <em>pdb</em> command is tied to a certain specific version.</p> <pre><code>$ ls -ald /usr/bin/pdb lrwxrwxrwx 1 root root 6 Jun 2 23:02 /usr/bin/pdb -&gt; pdb2.6 </code></pre> <p>Then, look at the first line of pdb2.6. It contains</p> <pre><code>#! /usr/bin/python2.6 </code></pre> <p>This is why <em>pdb</em> is stubborn and always seems to run under a specific version of Python. Because it really is! Actually, this sort of dependency makes sense for a piece of software like a symbolic debugger.</p> <p>I've compiled python2.7 from sources and pdb is not there, apparently. After some scrutiny, I found pdb.py for python-2.7, under the lib folder. I've then created some symlinks to it, for convenience:</p> <pre><code>$ cd /opt/python-dev ##-- this is where I installed from sources $ cd bin $ sudo ln -s ../lib/python2.7/pdb.py pdb2.7 $ sudo ln -s pdb2.7 pdb </code></pre> <p>Now observe the first line of pdb2.7. It reads:</p> <pre><code>#! /usr/bin/env python </code></pre> <p>... which looks better than the previous version. It basically means that pdb will be launched under the current Python you have defined in your environment, whatever it is, instead of anything hardcoded, like <em>/usr/bin/python</em> or <em>/usr/bin/python2.6</em> are. Good to know!</p> <p>I've also removed <em>pdb</em> and <em>pdb2.6</em> from system files, once I prefer to develop/debug inside virtualenv. Doing that, I will not be caught again by the same trick.</p> <p>I hope it helps.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload