Hello, On Wed, Jun 25, 2014 at 12:56:49PM -0700, Ben Longbons wrote: > On Wed, Jun 25, 2014 at 3:58 AM, Matthias Klose <d...@debian.org> wrote: > > Am 25.06.2014 00:51, schrieb Ben Longbons: > >> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose <d...@debian.org> wrote:
> >>> Are you aware of other pretty printers not > >>> working with python3? > >> From what I've seen, pretty printers that *do* work with python3 are a > >> very small minority. > > > > so for now the majority of pretty printers in Debian, afaics all of them, > > are > > able to use python3. > > As the other message showed, this claim was not true when you made it. > The impact of your packaging decisions is larger than you appear to > realize. Right, so it was temporarily reverted. > And golang-src is a great example of a case where Debian is currently > *failing* to ship python pretty-printers in the binary version of a > package. Is there an equivalent to CONTENTS but for source packages? You always can try codesearch.debian.net > If a python3-only gdb is desirable, the only sane migration strategy > that I can think of is: > - For jessie, ship gdb-python2 and gdb-python3 (since python3 is more > likely to have bugs, it should probably be the default, but switching > back to python2 and at any given moment is *absolutely* essential) > - For jessie+1, consider shipping only gdb-python3 (if that still > seems like a good idea, and there are no more migration problems that > have appeared) Exactly, I have been discussing over IRC a way forward with Matthias. Moving forward to python3 is something that needs to happen at some point. So, the proposal we have been discussing is very similar to your proposal. - For jessie, ship `gdb' built agains Python 3 and provide new package `gdb-python2' built against Python 2, with a news item estating that `gdb-python2' will be deprecated early on jessie+1 cycle. - For jessie+1, drop Python 2 support early in the cycle. Ben, do you agree on that, is it suitable for your needs? > Are you trying to make the claim that people shouldn't use platforms > other than Debian stable to develop software? Because (as someone who > write a lot of python) it is *far* from trivial to make python code > work *properly* on both python2 and python3. Please, don't make my > life more complicated than it needs to be for no reason at all. I need to apologize here, it was not my intention to make your life harder, please also understand the need to move forward. Please, do let me know what do you think about proposed strategy as I intend to make an upload with those changes ASAP. Best regards, -- Hector Oron
signature.asc
Description: Digital signature
