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 real source file.
- python gets re-installed every time you build.
Whats the reason for doing this? Can we get the same effect some other
way that doesn't involve duplicating all the .py files?
The root cause for this is that the python client needs to support
python 2.3, and to do this it needs to do some preprocessing on the
files before you can run them (assuming you're on a system with python
2.3). So it's not actually copying the files it's actually "compiling"
them, and the reason this is done under the cpp build root is simply to
not pollute the source tree.
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'm guessing it could be done in a smarter way
that wouldn't rebuild and wouldn't allow things to go stale.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
