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. Only files that are the same (like local scripts that run in both versions of Python) will be the same, but in that case, I would argue that you probably want the same breakpoints. Aaron Meurer > and I don't see a super-good > reason for keeping everything else separate. This would put a burden on > theme and stringifier developers to keep their code in the common subset > of Py2 and 3 if they care about having both, but that feels reasonable > to me. > > I'm not terribly worried about doing backward-incompatible things, since > PuDB has something like five settings total, so recreating them takes > about all of one minute, as long as we get it right now and then don't > have to mess with it for the foreseeable future. > > Andreas > _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
