Aaron Meurer <[email protected]> writes: > On Wed, Jul 31, 2013 at 3:12 PM, Andreas Kloeckner > <[email protected]> wrote: >> Aaron Meurer <[email protected]> writes: >> >>> On Wed, Jul 31, 2013 at 12:17 PM, Somchai Smythe >>> <[email protected]> wrote: >>>> I can see this has become some kind of holy war, and I'm not going to >>>> play that game. >>> >>> Really? I must have missed that part. >> >> What I'm really trying to do is figure out the right answer to the >> following questions: >> >> - Which settings should be kept separate for Python 3 and why? >> >> - What files/sections should they be kept in? >> >> I merged Somchai's original changes because I didn't have a strong >> opinion and thought, hey, here's someone who has thought about this, >> looks reasonable enough. >> >> I still don't have a strong opinion, since I'm mostly on Python 2, so I >> don't know the practicalities of using pudb from both languages. I >> sensed some disagreement among the people who actually do use pudb with >> Py2 and Py3. That's why I started this discussion. For what little bit >> of an opinion I've got, I could see keeping breakpoints separate by >> major version, just because, on average, they're going to point to a >> versioned installation directory anyhow, > > Actually, this *doesn't* make sense, because the breakpoints are the > full paths to files, so if they are in different installations, they > will automatically not transfer over.
Really? Where's the code to make that happen? If somebody sets a breakpoint in /usr/lib/python2.6/site-packages/something/or/another.py, what's keeping a Python 2.7 from picking up that breakpoint (which it will never hit)? Andreas
pgp3LndIdTu9q.pgp
Description: PGP signature
_______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
