On 24. Oct, 2010, at 6:02 , Tyler Roscoe wrote:
> On Sun, Oct 24, 2010 at 04:35:45AM +0200, Michael Hertling wrote:
>> On 10/24/2010 01:26 AM, Bill Spotz wrote:
>>> #! ${PYTHON_EXECUTABLE}
>
> Michael posted what I assume is a fantastic CMake solution :). Another
> approach you might consider i
On Sun, Oct 24, 2010 at 04:35:45AM +0200, Michael Hertling wrote:
> On 10/24/2010 01:26 AM, Bill Spotz wrote:
> > #! ${PYTHON_EXECUTABLE}
Michael posted what I assume is a fantastic CMake solution :). Another
approach you might consider is to use:
#!/usr/vin/env python
which works out of t
On 10/24/2010 01:26 AM, Bill Spotz wrote:
> Hi,
>
> Is there a standard way to make tests for python extension modules?
>
> Currently, I copy test scripts from the source directory to the binary
> directory. I would like to augment this by making the first line of my script
>
> #! ${PYTHON_E
Hi,
Is there a standard way to make tests for python extension modules?
Currently, I copy test scripts from the source directory to the binary
directory. I would like to augment this by making the first line of my script
#! ${PYTHON_EXECUTABLE}
but the only copy facility I see that supports
