Mailman 3 June 2012 - capi-sig

ANN: expy 0.6.5 released!
by Yingjie Lan 16 Apr '22

16 Apr '22

EXPY is an express way to extend Python! EXPY provides a way to extend python in an elegant way. For more information and a tutorial, see: http://expy.sourceforge.net/ What's new: 1. Correct treatment of __init__ method. 2. Give warnings of missing Py_INCREF on appropriate special type methods. 3. Documentation update. Cheers, Yingjie

3 3

ANNOUNCE: PyBindGen 0.8
by Gustavo Carneiro 10 Mar '22

10 Mar '22

The other day I released PyBindGen 0.8. Main news is that it features a new experimental header file scanner based on pygccxml (i.e., it's similar to py++ in scope, if not in maturity, but does not use boost.pythonunderneath). == What == PyBindGen is a Python module that is geared to generating C/C++ code that binds a C/C++ library for Python. It does so without extensive use of either C++ templates or C pre-processor macros. It has modular handling of C/C++ types, and can be easily extended with Python plugins. The generated code is almost as clean as what a human programmer would write, and does not depend on any library or header files besides Python itself. == Where == https://launchpad.net/pybindgen/ == NEWS == - Support C++ instance attributes through getter/setter methods - Support functions as methods of C++ classes - Support the PyObject* type - Support unsigned int, C strings (char*) (from Mark Lee) - Add basic support for enum types - New experimental automatic module generator based on C/C++ header file scanner and annotations in comments, using pygccxml - Some bug fixes -- Gustavo J. A. M. Carneiro INESC Porto, Telecommunications and Multimedia Unit "The universe is always one step beyond logic." -- Frank Herbert

2 1

C API equivalent to abc.ABCMeta.register?
by Daniel Stutzbach 02 Mar '22

02 Mar '22

I'm the author of an extension module (blist) that provides a type that fits the MutableSequence API. Is there a canonical way for me to register the type as a MutableSequence from the C API? -- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com>

3 2

Software Development - Application Development - Game Development
by Gary 10 Jan '22

10 Jan '22

You are receiving this email because we wish you to use our cost-effective IT services. We are a China based Custom Software Application Development provider. We offer full cycle custom software programming services, from product idea, software development to support and enhancement. We employ a large pool of software engineers coming from different backgrounds. We are able to balance product development efforts and project duration to your business needs. Core Services: Custom Application Development Custom Software Development iPhone Application Development iPad Application Development Mobile Application Development Android Mobile Application Development Soft Product Development Game Design & Development Game Testing & Quality Assurance Cloud Computing Solutions: CRM Software Application Development ERP Software Application Development Enterprise Portal Solution Sales Force Automation Solution Game Design & Development Knowledge Management Solution Workflow Management Solution SharePoint Development Services Microsoft Online Services Microsoft Azure Services Best regards, Gary ITVIATSA Software Development Contact: ibsoftware(a)yeah.net Pls send address to larryremove123(a)msn.com for remove

2 2

Re: [capi-sig] Embedding basics
by Philip Semanchuk 28 Jun '12

28 Jun '12

On Jun 28, 2012, at 4:35 PM, ecir hana wrote: > > - How to build Python myself? "./configure" and "make" works but > I'm afraid to do "make install" as it might mess with pre-installed Python, > am I right? And it creates lots of .so, and no .a's. Hi Ecir, It's been a while since I compiled Python, but in the README supplied with the source code it talks about installation options. By default it installs in the /usr/local tree which should not interfere with your system Python. > Even if I somehow > manage to build Python and test.c what if it uses some libraries? Do I have > to somehow compile and link them to the one big executable as well or is it > just matter of packing the libraries along the binary and setting the > Python find path? Installing Python will put the runtime libraries on your system. If you want to run your program on a system where Python isn't installed, you need a 3rd party program like PyInstaller, Py2App, Py2Exe, bbfreeze, cx_freeze, etc. Hope this helps Philip > > > > > On Thu, Jun 28, 2012 at 2:27 PM, Henrique <typoon(a)gmail.com> wrote: > >> Hey Ecir, >> >> By reading your email, I think you might want to first learn some basic >> concepts about C programming and how a program can be linked to dynamic or >> static libraries. >> When Python is compiled in your machine, a dynamic or a static (or both) >> library built, which you use to link with your program (your test.c). If >> MacOS provides binaries for Python, I believe the libraries might alreayd >> be there, and you might not need to compile it manually. (based on what you >> are saying, you are only trying to compile it because you thought that is >> how it should be done to have your test.c file to work). If you are still >> interested in compiling it yourself, I believe there should be instructions >> with the source (perhaps an INSTALL file there, explaining it). I am not >> sure as I do not currently have the source here with me (but it should be >> as simple as running ./configure && make && make install). >> After you have Python compiled and running on your machine, you will write >> source that will use the functions provided by the Python library in your >> application, that is where your 'test.c' program comes into play. >> >> Some time ago I wrote some introduction blog posts about the Python C API. >> If you are interested, this might help you a little bit >> http://www.gilgalab.com.br/2011/05/03/python-c-api-first-step/ >> http://www.gilgalab.com.br/2011/05/03/python-c-api-second-step/ >> >> But again, I really think you should look up some basics on C development >> in a Unix platform :) >> >> Regards, >> >> Henrique >> >> >> On Thu, Jun 28, 2012 at 6:08 AM, ecir hana <ecir.hana(a)gmail.com> wrote: >> >>> Hello, >>> >>> please, I have a bit of trouble grasping a few very basic concepts related >>> to Python embedding, could someone explain those to me? >>> >>> What I try to achieve is to have single one (big) binary, which contains >>> my >>> Python script, the wrapper and Python interpreter itself, I'm on MacOS >>> 10.6. My questions are: >>> >>> - I would like to build Python myself. I downloaded Python 3.3 beta source >>> code, extracted it in a folder. Next to "Python-3.3.0b1" folder, there is >>> a >>> file "test.c" which contains: >>> >>> #include <Python.h> >>> >>> int >>> main(int argc, char *argv[]) >>> { >>> Py_Initialize(); >>> PyRun_SimpleString("from time import time,ctime\n" >>> "print('Today is', ctime(time()))\n"); >>> Py_Finalize(); >>> return 0; >>> } >>> >>> Now, what should I do next? I though I would just "somehow" compile and >>> link Python source code with test.c and that's it but when I do "gcc -I >>> ./Python-3.3.0b1 -o test test.c" I get lots of errors. (Note: I'm total >>> noob what this whole gcc and static linking and .a files goes...) >>> >>> - Next I tried to run "./configure" and "make". It finished without errors >>> and it creates "build/lib.macosx-10.6-x86_64-3.3" folder with lots of *.so >>> (?) files but I'm not sure how to make use of them. >>> >>> If building everything from scratch (the first step above) is not an >>> option, what do I need to build? A "framework"? .dylib? .a? And than link >>> test.o against that? >>> >>> - How does Python from python.org get build? Do they use the same >>> "./configure" and "make" as I can? Do they use any special option? >>> >>> To summarize, I have Python source code and test.c and I would like to >>> have >>> one executable which says "Today is ....". Could someone, please, explain >>> in layman terms, the necessary steps? >>> >>> Thanks you very much in advance! >>> >>> Ecir Hana >>> _______________________________________________ >>> capi-sig mailing list >>> capi-sig(a)python.org >>> http://mail.python.org/mailman/listinfo/capi-sig >>> >> >> > _______________________________________________ > capi-sig mailing list > capi-sig(a)python.org > http://mail.python.org/mailman/listinfo/capi-sig

1 0

Re: [capi-sig] Embedding basics
by ecir hana 28 Jun '12

28 Jun '12

Hello Henrique, Mateusz, thank you both for the replies! Yes, I would like to compile it myself (as opposite to using the libraries already installed). I don't really have a problem with Python C API, ref counting, creating Python objects in C and such stuff. My problem is perhaps two fold: - I don't know how is it called what I need to do in order to have one big fat executable. Do I need a library which I can statically link agains? Is this the "libpython.a" on some systems? From what I understood, if I want to have just one binary I have to link "statically", correct? That is, I have to have this ".a" file (what is it called on MacOS?) because .dll (on Windows?) is used dynamically. So, either do I need ".a" (or MacOS equivalent) or is it possible to somehow compile Python source together with test.c in one go, avoiding the creation of Python library? Or do I have to do it completely different of MacOS (frameworks et al.)? - How to build Python myself? "./configure" and "make" works but I'm afraid to do "make install" as it might mess with pre-installed Python, am I right? And it creates lots of .so, and no .a's. Even if I somehow manage to build Python and test.c what if it uses some libraries? Do I have to somehow compile and link them to the one big executable as well or is it just matter of packing the libraries along the binary and setting the Python find path? On Thu, Jun 28, 2012 at 2:27 PM, Henrique <typoon(a)gmail.com> wrote: > Hey Ecir, > > By reading your email, I think you might want to first learn some basic > concepts about C programming and how a program can be linked to dynamic or > static libraries. > When Python is compiled in your machine, a dynamic or a static (or both) > library built, which you use to link with your program (your test.c). If > MacOS provides binaries for Python, I believe the libraries might alreayd > be there, and you might not need to compile it manually. (based on what you > are saying, you are only trying to compile it because you thought that is > how it should be done to have your test.c file to work). If you are still > interested in compiling it yourself, I believe there should be instructions > with the source (perhaps an INSTALL file there, explaining it). I am not > sure as I do not currently have the source here with me (but it should be > as simple as running ./configure && make && make install). > After you have Python compiled and running on your machine, you will write > source that will use the functions provided by the Python library in your > application, that is where your 'test.c' program comes into play. > > Some time ago I wrote some introduction blog posts about the Python C API. > If you are interested, this might help you a little bit > http://www.gilgalab.com.br/2011/05/03/python-c-api-first-step/ > http://www.gilgalab.com.br/2011/05/03/python-c-api-second-step/ > > But again, I really think you should look up some basics on C development > in a Unix platform :) > > Regards, > > Henrique > > > On Thu, Jun 28, 2012 at 6:08 AM, ecir hana <ecir.hana(a)gmail.com> wrote: > >> Hello, >> >> please, I have a bit of trouble grasping a few very basic concepts related >> to Python embedding, could someone explain those to me? >> >> What I try to achieve is to have single one (big) binary, which contains >> my >> Python script, the wrapper and Python interpreter itself, I'm on MacOS >> 10.6. My questions are: >> >> - I would like to build Python myself. I downloaded Python 3.3 beta source >> code, extracted it in a folder. Next to "Python-3.3.0b1" folder, there is >> a >> file "test.c" which contains: >> >> #include <Python.h> >> >> int >> main(int argc, char *argv[]) >> { >> Py_Initialize(); >> PyRun_SimpleString("from time import time,ctime\n" >> "print('Today is', ctime(time()))\n"); >> Py_Finalize(); >> return 0; >> } >> >> Now, what should I do next? I though I would just "somehow" compile and >> link Python source code with test.c and that's it but when I do "gcc -I >> ./Python-3.3.0b1 -o test test.c" I get lots of errors. (Note: I'm total >> noob what this whole gcc and static linking and .a files goes...) >> >> - Next I tried to run "./configure" and "make". It finished without errors >> and it creates "build/lib.macosx-10.6-x86_64-3.3" folder with lots of *.so >> (?) files but I'm not sure how to make use of them. >> >> If building everything from scratch (the first step above) is not an >> option, what do I need to build? A "framework"? .dylib? .a? And than link >> test.o against that? >> >> - How does Python from python.org get build? Do they use the same >> "./configure" and "make" as I can? Do they use any special option? >> >> To summarize, I have Python source code and test.c and I would like to >> have >> one executable which says "Today is ....". Could someone, please, explain >> in layman terms, the necessary steps? >> >> Thanks you very much in advance! >> >> Ecir Hana >> _______________________________________________ >> capi-sig mailing list >> capi-sig(a)python.org >> http://mail.python.org/mailman/listinfo/capi-sig >> > >

1 0

Re: [capi-sig] Embedding basics
by Mateusz Loskot 28 Jun '12

28 Jun '12

On 28 June 2012 13:27, Henrique <typoon(a)gmail.com> wrote: > By reading your email, I think you might want to first learn some basic > concepts about C programming and how a program can be linked to dynamic or > static libraries. I second that piece of advice. > Some time ago I wrote some introduction blog posts about the Python C API. > If you are interested, this might help you a little bit > http://www.gilgalab.com.br/2011/05/03/python-c-api-first-step/ > http://www.gilgalab.com.br/2011/05/03/python-c-api-second-step/ I'd also suggest to watch Ned Batchelder's talk from PyCon 2009 in Chicago: A Whirlwind Excursion through Python C Extensions http://nedbatchelder.com/text/whirlext.html Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

Re: [capi-sig] Embedding basics
by Henrique 28 Jun '12

28 Jun '12

Hey Ecir, By reading your email, I think you might want to first learn some basic concepts about C programming and how a program can be linked to dynamic or static libraries. When Python is compiled in your machine, a dynamic or a static (or both) library built, which you use to link with your program (your test.c). If MacOS provides binaries for Python, I believe the libraries might alreayd be there, and you might not need to compile it manually. (based on what you are saying, you are only trying to compile it because you thought that is how it should be done to have your test.c file to work). If you are still interested in compiling it yourself, I believe there should be instructions with the source (perhaps an INSTALL file there, explaining it). I am not sure as I do not currently have the source here with me (but it should be as simple as running ./configure && make && make install). After you have Python compiled and running on your machine, you will write source that will use the functions provided by the Python library in your application, that is where your 'test.c' program comes into play. Some time ago I wrote some introduction blog posts about the Python C API. If you are interested, this might help you a little bit http://www.gilgalab.com.br/2011/05/03/python-c-api-first-step/ http://www.gilgalab.com.br/2011/05/03/python-c-api-second-step/ But again, I really think you should look up some basics on C development in a Unix platform :) Regards, Henrique On Thu, Jun 28, 2012 at 6:08 AM, ecir hana <ecir.hana(a)gmail.com> wrote: > Hello, > > please, I have a bit of trouble grasping a few very basic concepts related > to Python embedding, could someone explain those to me? > > What I try to achieve is to have single one (big) binary, which contains my > Python script, the wrapper and Python interpreter itself, I'm on MacOS > 10.6. My questions are: > > - I would like to build Python myself. I downloaded Python 3.3 beta source > code, extracted it in a folder. Next to "Python-3.3.0b1" folder, there is a > file "test.c" which contains: > > #include <Python.h> > > int > main(int argc, char *argv[]) > { > Py_Initialize(); > PyRun_SimpleString("from time import time,ctime\n" > "print('Today is', ctime(time()))\n"); > Py_Finalize(); > return 0; > } > > Now, what should I do next? I though I would just "somehow" compile and > link Python source code with test.c and that's it but when I do "gcc -I > ./Python-3.3.0b1 -o test test.c" I get lots of errors. (Note: I'm total > noob what this whole gcc and static linking and .a files goes...) > > - Next I tried to run "./configure" and "make". It finished without errors > and it creates "build/lib.macosx-10.6-x86_64-3.3" folder with lots of *.so > (?) files but I'm not sure how to make use of them. > > If building everything from scratch (the first step above) is not an > option, what do I need to build? A "framework"? .dylib? .a? And than link > test.o against that? > > - How does Python from python.org get build? Do they use the same > "./configure" and "make" as I can? Do they use any special option? > > To summarize, I have Python source code and test.c and I would like to have > one executable which says "Today is ....". Could someone, please, explain > in layman terms, the necessary steps? > > Thanks you very much in advance! > > Ecir Hana > _______________________________________________ > capi-sig mailing list > capi-sig(a)python.org > http://mail.python.org/mailman/listinfo/capi-sig >

1 0

Embedding basics
by ecir hana 28 Jun '12

28 Jun '12

Hello, please, I have a bit of trouble grasping a few very basic concepts related to Python embedding, could someone explain those to me? What I try to achieve is to have single one (big) binary, which contains my Python script, the wrapper and Python interpreter itself, I'm on MacOS 10.6. My questions are: - I would like to build Python myself. I downloaded Python 3.3 beta source code, extracted it in a folder. Next to "Python-3.3.0b1" folder, there is a file "test.c" which contains: #include <Python.h> int main(int argc, char *argv[]) { Py_Initialize(); PyRun_SimpleString("from time import time,ctime\n" "print('Today is', ctime(time()))\n"); Py_Finalize(); return 0; } Now, what should I do next? I though I would just "somehow" compile and link Python source code with test.c and that's it but when I do "gcc -I ./Python-3.3.0b1 -o test test.c" I get lots of errors. (Note: I'm total noob what this whole gcc and static linking and .a files goes...) - Next I tried to run "./configure" and "make". It finished without errors and it creates "build/lib.macosx-10.6-x86_64-3.3" folder with lots of *.so (?) files but I'm not sure how to make use of them. If building everything from scratch (the first step above) is not an option, what do I need to build? A "framework"? .dylib? .a? And than link test.o against that? - How does Python from python.org get build? Do they use the same "./configure" and "make" as I can? Do they use any special option? To summarize, I have Python source code and test.c and I would like to have one executable which says "Today is ....". Could someone, please, explain in layman terms, the necessary steps? Thanks you very much in advance! Ecir Hana

1 0

PyGILState_Ensure/PyGILState_Release
by Bob Rossi 27 Jun '12

27 Jun '12

Hi, I'm really having trouble understanding the python threading model. It's clear to me from the docs, http://docs.python.org/py3k/c-api/init.html?highlight=initthread that I need to initialize python as so when requiring the use of threads, Py_Initialize(); PyEval_InitThreads(); Then, after that point, in each new thread, I should use PyGILState_STATE state = PyGILState_Ensure(); // python code PyGILState_Release(state); A few questions arise which do not seem to be documented clearly. It's not clear to me if a call to Ensure locks python into executing only in that thread until Release is called, or if it's just a registration function which then allows python to choose which python code it would like to execute in which thread at which time. Can anyone answer this? Based on my confusion above, I'm wondering if I can wrap the Ensure/Release calls around the entire new thread, or should this be done around a small snippet of python code? What are the trade offs? Finally, I notice that after my call to PyEval_InitThreads() I had to call PyEval_SaveThread(); in order to allow other threads to call PyGILState_Ensure() with out blocking forever. This is not documented. I'm not sure I'm doing the correct thing here. Any ideas? Thanks, Bob

2 1

capi-sig June 2012