This bug was fixed in the package sabnzbdplus - 0.5.6-1ubuntu1
---
sabnzbdplus (0.5.6-1ubuntu1) natty; urgency=low
* Unblock Python 2.7 from pyversions (LP: #689274)
-- Stefano RiveraSun, 12 Dec 2010 19:45:57 +0200
** Branch linked: lp:ubuntu/sabnzbdplus
** Changed in: sabnzb
I was unaware of that announcement (as I am more of an experienced user
than a developer) but I just manually installed it from the package and
it works for me too, so I would support the usage of Python 2.7 too.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
> I am unaware of any announcement of ubuntu's plans for 2.7
https://lists.ubuntu.com/archives/ubuntu-devel-
announce/2010-December/000795.html
> Once this was successfully tested in natty, I'll update the packaging
in Debian too.
I'll take that as a vote from you that I should update the packag
For upstream and 2.7, it's simply not tested and thus not supported by
them (yet). On their forum, a number of people have been running the
program with python 2.7, apparently without major issues. Once this was
successfully tested in natty, I'll update the packaging in Debian too.
I am unaware of
> I'd suggest at least temporarily changing the dependencies
There's no * desperate* rush here, the transition was well announced and
people can expect some breakage of this sort for a week or two.
As far as I can see, upstream just doesn't *test* 2.7, they don't say it
won't work. I'm tempted to
And because of that the package can currently not be installed at least
in Natty. I'd suggest at least temporarily changing the dependencies
from python >= 2.4 and python < 2.7 to python2.6 so we can install it
again.
apt-get output:
# apt-get install sabnzbdplus
> Reading package lists... Done
>
