After some research i recognized that python-tqt and python-trinity-trinity 
are depending on python-sip-tqt and not python-sip.

python-tqt is working and importing sip from python-sip-tqt, while 
python-trinity-trinity does not work and seem to use another importing 
algorithm.

I've no clue if this is a bug or i'm doing something wrong. I'm also not 
familiar with SIP.

On Monday 25 September 2017 03:08:44 Richard Lamboj wrote:
> Hello,
>
> unfortunately, using python-trinity-trinity ends for me with a segmentation
> fault.
>
> What I've done:
> ~ python
> Python 2.7.14 (default, Sep 17 2017, 18:50:44)
> [GCC 7.2.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> >>> import tdecore
>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError: PyCapsule_Import could not import module "sip"
>
> # apt-get install python-sip
>
> ~ python
> Python 2.7.14 (default, Sep 17 2017, 18:50:44)
> [GCC 7.2.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> >>> import tdefile
>
> Segmentation fault
>
> # dpkg -l python-trinity-trinity
> Desired=Unknown/Install/Remove/Purge/Hold
>
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-p
> |end / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> |
> ||/ Name                           Version              Architecture
>
> Description
> +++-==============================-====================-===================
>=-================================================================= ii 
> python-trinity-trinity         4:14.0.5~pre6-0debia amd64
> Trinity bindings for Python [Trinity]
>
> Kind Regards,


-- 
Richard Lamboj
Geschäftsführung
unicom e. U.

http://unicom.ws/
rl@...
+43 (0)676 7568629