Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Dec 2016 10:05:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 215488] databases/py-sqlparse: "cannot import name offset" on current 2016Q4
Message-ID:  <bug-215488-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215488

            Bug ID: 215488
           Summary: databases/py-sqlparse: "cannot import name offset" on
                    current 2016Q4
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: sergey@blender.org
          Assignee: sunpoet@FreeBSD.org
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)

Created attachment 178200
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178200&action=
=3Dedit
Full python traceback of the issue

Hi,

Current version of py-sqlparse from 2016Q4 throws an import exception when
importing migrate.versioning.repository.

It's simple to reproduce:

% python2
>> import migrate.versioning.repository

The full traceback is attached.

This module is used by buildbot master, so effectively it is also broken
currently.

I can see there's py-sqlparse 0.2.2 in the trunk ports, so perhaps it's a
matter of merging that into Q4 ports?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215488-13>