> With Cython, it doesn't work, because the .so files don't find each other. > > One solution (besides moving __init__.py files away at each build) is > to just create an option to cython, that will disable this feature (or > pretend the __init__.py files are not there). > > I am not convinced it's worth the pain though yet. So you think one > should never need to segregate the .so file in a Python + C++ project?
I think this should function like the --inplace option to distutils. Once built, the .so's/.dylibs should be moved into the source tree if the build is inplace. Either that, or the .py files should all be moved over to the out of place build location. I think trying to run things in a fragmented manner like you are describing is confusing and is going to cause unneeded pain. Cheers, Brian > Ondrej > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
