[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] Dependency on sip.pyd
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2006-11-10 19:31:06
Message-ID: 200611101931.06529.phil () riverbankcomputing ! co ! uk
[Download RAW message or body]

On Friday 10 November 2006 7:19 pm, Giovanni Bajo wrote:
> Phil Thompson wrote:
> > Sorry, I don't think I understand what you mean.
>
> What I would like to obtain is that modules generated by SIP do not depend
> on an external module (sip.pyd). This is technically possible of course,
> it's just that SIP was designed in a different way.
>
> > sip.pyd is a Python extension module - it is not a library and it is
> > not linked against.
>
> This is the current design, I'm asking to add an option to change this.
>
> > You can build it statically and have it built in
> > to your Python interpreter - same for PyQt (though I don't test
> > this). So you could create a project specific interpreter.
>
> To be clear, I'm not speaking of embedding sip.pyd in python.dll as a
> builtin module. I'm speaking of totally *removing* sip.pyd as a module, and
> just "put" all the necessary code within my own extension module created by
> SIP.

...just like SIP v0.1 used to work. No, I'm not going to do that.

Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]