Re: [pypy-dev] File overwriting (--output flag to translate.py)

2011-04-12 Thread Carl Friedrich Bolz
On 04/11/2011 02:45 PM, p...@pocketnix.org wrote: > Hi again > > i have been compiling a bunch of different pypy instances with different > levels of optimizations and features and found that if i run pypy-c > from the current directory and dont specify a new output filename it > will attempt to an

Re: [pypy-dev] File overwriting (--output flag to translate.py)

2011-04-12 Thread pypy
On Mon, Apr 11, 2011 at 09:27:09PM +0200, Armin Rigo wrote: > > Sadly everyone so far has his own additional hacks to categorize > multiple translated versions. Mine is to ignore the pypy-c entirely > and copy the executable from the /tmp, after it has been produced > there. I also copy the C so

Re: [pypy-dev] File overwriting (--output flag to translate.py)

2011-04-11 Thread Armin Rigo
Re-Hi, On Mon, Apr 11, 2011 at 2:45 PM, wrote: > +        # Ensure the file does not exisit else we fail at end of translation > +        if os.path.isfile(drv.exe_name): > +            raise ValueError('File "' + drv.exe_name+ '" already exisits > (--output)') Sadly everyone so far has his ow

[pypy-dev] File overwriting (--output flag to translate.py)

2011-04-11 Thread pypy
Hi again i have been compiling a bunch of different pypy instances with different levels of optimizations and features and found that if i run pypy-c from the current directory and dont specify a new output filename it will attempt to and fail to overwrite pypy-c due to the file being "in use"