Fixed in Karmic.
** Changed in: sqlalchemy (Ubuntu)
Importance: Undecided = Low
** Changed in: sqlalchemy (Ubuntu)
Status: Confirmed = Fix Released
--
/var/lib/python-support/python2.6/sqlalchemy/ext/activemapper.py:262:
SyntaxWarning: assertion is always true, perhaps remove
Confirmed on a post-release install of python-sqlalchemy alone.
** Changed in: sqlalchemy (Ubuntu)
Status: New = Confirmed
--
/var/lib/python-support/python2.6/sqlalchemy/ext/activemapper.py:262:
SyntaxWarning: assertion is always true, perhaps remove parentheses?
I get a similar message when try to install a package.
My system is Jaunty right after `apt-get update apt-get upgrade`
--
/var/lib/python-support/python2.6/sqlalchemy/ext/activemapper.py:262:
SyntaxWarning: assertion is always true, perhaps remove parentheses?
I've got the same error with a Jaunty daily-build of 13-Apr-2009:
...
Setting up avant-window-navigator (0.3.2-0ubuntu1) ...
Setting up awn-manager (0.3.2-0ubuntu1) ...
Setting up awn-applets-c-core (0.3.2.1-0ubuntu2) ...
Setting up awn-applets-python-core (0.3.2.1-0ubuntu2) ...
Processing
** Attachment added: dpkg log from the installation
http://launchpadlibrarian.net/24051053/dpkg.log
--
/var/lib/python-support/python2.6/sqlalchemy/ext/activemapper.py:262:
SyntaxWarning: assertion is always true, perhaps remove parentheses?
https://bugs.launchpad.net/bugs/344884
You
FTR: problem doesn't exist in python-sqlalchemy 0.5.2-1 (and all reverse
dependencies are already 0.5 compatible in Debian unstable)
--
/var/lib/python-support/python2.6/sqlalchemy/ext/activemapper.py:262:
SyntaxWarning: assertion is always true, perhaps remove parentheses?
So it looks like I picked it up as a dependency to awn-applets-python-
core. Does that mean that awn-applets-python-core dependencies need to
be updated (along with all the others) to point depend on 0.5.2-1? Or
if all of them are compatible then perhaps 0.5.2-1 should be the only
option for
from that list: anki and python-migrate are still not compatible and
need syncing, see also #316429
BTW: fixing this bug should be easy, though (assert(...) is used only in
one line in 0.4.8-1)
(I will not provide patch as there's no python2.6 in Debian yet)
--
