Re: [Python-modules-team] Bug#806334: kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random'

Brian May writes: > Don't think we can complain at Python though, looks like a private > symbol. Looks like this is a work around for a bug that was in Python 2.5. http://bugs.python.org/issue4607: >From kombu code: def uuid4(): # Workaround for

Re: Pushing a bunch of packages to jessie-backports

On Fri, Nov 27, 2015 at 8:02 PM, Thomas Goirand wrote: > That's one of the multiple breakage that the NEW queue brings. There's > unfortunately no way to fix that for this kind of complex uploads with > inter-dependencies and updates of existing packages. The only way, > unfortunately, is to have

Re: Packaging Python that requires 3.5

Hi Brian, On Sat, Nov 28, 2015 at 05:08:20PM +1100, Brian May wrote: > Apparently this doesn't work just yet. > > In debian/control I have X-Python3-Version: >= 3.5 > > This gives in the Depends: > python3.5:any, python3:any (>= 3.5~) > > This cannot be statisfied because python3 the version in

Re: Request to join the team

[Dariusz Dwornikowski, 2015-11-24] > I would like to join the DPMT team to help maintaining python welcome :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7

Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Brian May writes: > However I don't know much about this Python 3.5 transition, or what > the current waiting point is. API/ABI transitions (such as switching default Python 3 to be PYthon 3.5) are managed by the release team, with a workflow described at

Re: Packaging Python that requires 3.5

Dmitry Shachnev writes: > I recommend simply waiting until 3.5 is the default (do we have any ETA > for that?). Good question. If it was anytime soon, I would wait. However I don't know much about this Python 3.5 transition, or what the current waiting point is. Is there

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Scott Kitterman writes: > We haven't started the transition yet. When it starts, binNMU should > be enough for most of the packages. When will you start the transition? -- Brian May

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

On November 28, 2015 7:21:57 PM EST, Brian May wrote: >Ben Finney writes: > >> API/ABI transitions (such as switching default Python 3 to be PYthon >> 3.5) are managed by the release team, with a workflow described at >>

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Ben Finney writes: > API/ABI transitions (such as switching default Python 3 to be PYthon > 3.5) are managed by the release team, with a workflow described at > . There is