Re: Why do we create the cpp/src/tests/python dir?

2010-03-19 Thread Rafael Schloming
Alan Conway wrote: The C++ builds install python files in src/tests/python. This is kind of a pain for at least 2 reasons: - src/tests/python can go stale - not sure how but it just happened to me. - debugging python code, error messages take you to the src/tests/python copy rather than the

Re: Why do we create the cpp/src/tests/python dir?

2010-03-19 Thread Alan Conway
On 03/19/2010 07:59 AM, Rafael Schloming wrote: Alan Conway wrote: The C++ builds install python files in src/tests/python. This is kind of a pain for at least 2 reasons: - src/tests/python can go stale - not sure how but it just happened to me. - debugging python code, error messages take you

Re: Why do we create the cpp/src/tests/python dir?

2010-03-19 Thread Andrew Stitcher
On Fri, 2010-03-19 at 07:59 -0400, Rafael Schloming wrote: As for why they get re-installed every time and how they can go stale, I'm not sure about that. I believe andrew was the one who modified the cpp build to do this. I plead not guilty m'lud.

Re: Why do we create the cpp/src/tests/python dir?

2010-03-19 Thread Rafael Schloming
Gordon Sim wrote: On 03/19/2010 02:23 PM, Alan Conway wrote: I think the clean way out is to make the python project a dependency of the C++ project just like it depends on boost or other tools. I.e. to run the tests you must *install* the python project, and the tests pick up components via

Why do we create the cpp/src/tests/python dir?

2010-03-16 Thread Alan Conway
The C++ builds install python files in src/tests/python. This is kind of a pain for at least 2 reasons: - src/tests/python can go stale - not sure how but it just happened to me. - debugging python code, error messages take you to the src/tests/python copy rather than the real source file. -