Jari Aalto wrote: > * Fri 2008-03-07 Robert Kern <[EMAIL PROTECTED]> gmane.comp.python.general > * Message-Id: [EMAIL PROTECTED] > >>>>> setup(name='program', >>> ... >>>>> scripts = ['program,py'], >>>>> ) >>>>> that the the result is: >>>>> >>>>> /usr/bin/program >>>>> >>>>> instead of: >>>>> >>>>> /usr/bin/program.py >>>> The easiest and best way is to just rename the file in your source tree to >>>> "program" and be done with it. >>> Is there any other way? This is the source package that I would like >>> to keep intact and just patch the setup.py >> Not really, no. Why is it so important to only patch the setup.py >> file and not any others? > > It has to do with generating a diff against the original package. If > the file is moved: > > mv file.py file > > prior setup.py run (which, according to answers, would have a change > to <<scripts = ['program']>>), the problem is the generated diff > against original sources: > > + would flag removal of 'file.py' > + inclusion of 'file' > > The ideal would be if setup.py could do all the destination install > "postwork". The generated patch would be clean and only contain > changes in setup.py. > > But I understand, if distutils does not support stripping the > extensions during install. It just cacuses exra work for utility > packagers.
What build system are you using that doesn't let you execute cp file.py file before running the setup.py? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
