Le 15 nov. 2011 à 17:15, Jérôme Laheurte a écrit : > > Le 15 nov. 2011 à 16:20, Jim Bosch a écrit : > >> On 11/15/2011 10:00 AM, Olivier Voyer wrote: >>> Jim, thank you for your answer. >>> >>> What if I have this big C++ project that I cannot split in multiple >>> smaller projects? I have no choice but to create a big Python module >>> exposing all the functions/classes? What is the common practice? >>> >> >> It sounds like you just want to make a Python package - a directory with an >> __init__.py file that contains all your submodules, which can each be >> compiled separately. >> >> Is there some reason you felt you needed to put all the modules in the same >> pyd file? > > To share common structures/classes without having to use a PyCObject. > Actually that's rather theoretical, I never actually needed this, just > curious.
Nevermind, that's a silly reason. Of course I can just use the same classes from different .so files (as long as I rebuild them all when I change a declaration). _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
