From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-03-05 13:36:17
Stefan Seefeld wrote:
> The attached patch appears to fix the problem with the import_ test.
> Here is how it works:
> * The py-run rule now allows an optional input-file argument.
> * The import_ test invocation takes the import_.py file as argument,
> which bjam magically turns into a relative path.
> * The import_.cpp code extracts that path, and injects it into the
> module search path, before attempting to 'import import_'.
> Thanks to Volodya for helping me with the boost.build change.
> OK to check in ?
The build-system-related changes seem fine with me. I can't
comment on Boost.Python code with confidence, but nothing
jumped on me either.
Thomas, can this go in?
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk