Date: Fri, 13 Jul 2007 21:12:33 +0200 From: "Mathieu Prevot" <mathieu.prevot@gmail.com> To: "Joseph Koshy" <jkoshy@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: python modules Message-ID: <3e473cc60707131212u1e3b4552v2dfc5c10cfe8e533@mail.gmail.com> In-Reply-To: <3e473cc60707131205s1a2912c3p9895832de54e6b94@mail.gmail.com> References: <3e473cc60707131205s1a2912c3p9895832de54e6b94@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2007/7/13, Mathieu Prevot <mprevot@freebsd.org>: > I learn that modules loaded with import fall into 4 general categories: > - code written in Python (.py) > - C or C++ extensions that have been compiled into shared libraries (or DLLs) > - Packages containing collection of modules > - Built-in modles writen in C and linked into the Python interpreter > > Why don't we use directly the libpmc library in C instead of rewritting > things in python ? I copied libpmc.so and tryed 'import libpmc'. I have: ImportError: dynamic module does not define init function (initlibpmc) Are we really far from having a libpmc module ? Mathieu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e473cc60707131212u1e3b4552v2dfc5c10cfe8e533>