[Python-modules-team] Bug#739476: ImportError: cannot import name ScopedSession

Arnaud Fontaine arnau at debian.org
Wed Feb 19 05:28:17 UTC 2014


Source: elixir
Severity: grave
Tags: upstream

Hello,

When trying to import elixir module, I get the following traceback which
makes elixir completely unusable:

import elixir
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/pymodules/python2.7/elixir/__init__.py", line 29, in <module>
    from elixir.entity import Entity, EntityBase, EntityMeta, EntityDescriptor, \
  File "/usr/lib/pymodules/python2.7/elixir/entity.py", line 17, in <module>
    from sqlalchemy.orm import MapperExtension, mapper, object_session, \
ImportError: cannot import name ScopedSession

Also, considering that a security bug, #670919, which is almost two
years old has never been fixed and there has been no upstream release
since 11/2009 (actually around the time a declarative layer has been
implemented in sqlalchemy AFAIU), I'm wondering whether this package
should be kept in the archive at all. What do you think?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Regards,
-- 
Arnaud Fontaine



More information about the Python-modules-team mailing list