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
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
>> https://wiki.debian.org/Teams/ReleaseTeam/Transitions>.
>
>There is https:
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
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions>.
There is https://release.debian.org/transitions/html/python3.5.html
Still tryi
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
https://wiki.debian.org/Teams/ReleaseTea
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 anything that can be d
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 un
[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 AEF
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
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 http://bugs.python.org/issue4607
if ctyp
9 matches
Mail list logo
