Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment:
>________________________________
>NO. I removed the 'copy_scripts' function, so I did not use your developed
>functionality. After this change, Packaging module now just builds new-style
>scripts and old-style scripts will be built by distutils/setuptools. To
>support the old-style scripts generated by d*/s* in p*, we can use the
>resource system.
>
>Not just as is, I believe. When scripts are installed (as opposed to other
>resources), it's not enough to copy them across to the configured destination:
>you also need to change their shebang lines to point to the appropriate Python
>executable. This is particularly important in virtualenvs where there could be
>any number of Python executables (of different versions) represented. But how
>will we know which .py files mentioned in resources are data, and which are
>actually scripts?
To me, it actually makes more sense to keep those scripts in the [scripts]
section, and have some way of recognising which scripts need to be
copied/amended and which ones need to be generated from callables.
----------
Added file: http://bugs.python.org/file22934/unnamed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12394>
_______________________________________
<html><body><div style="color:#000; background-color:#fff; font-family:tahoma,
new york, times, serif;font-size:10pt"><div id="yiv1385342022"><div
style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family:
tahoma,new york,times,serif; font-size: 10pt;"><div
id="yiv1385342022yui_3_2_0_14_131368247675778"><br><blockquote
id="yiv1385342022yui_3_2_0_14_131368247675754" style="border-left: 2px solid
rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div
id="yiv1385342022yui_3_2_0_14_131368247675785"
class="yiv1385342022yui_3_2_0_14_131368247675757" style="font-family:
tahoma,new york,times,serif; font-size: 10pt;"><div
id="yiv1385342022yui_3_2_0_14_131368247675784"
class="yiv1385342022yui_3_2_0_14_131368247675759" style="font-family: times new
roman,new york,times,serif; font-size: 12pt;"><font
id="yiv1385342022yui_3_2_0_14_131368247675783" face="Arial" size="2"><hr
size="1"><b id="yiv1385342022yui_3_2_0_14_131368247675782"><span
id="yiv1385342022yui_3_2_0_14_131368247675781" style="font-weight:
bold;"></span></b></font>NO. I removed the 'copy_scripts' function, so I did
not use your developed functionality. After this change, Packaging module now
just builds new-style scripts and old-style scripts
will be built by distutils/setuptools. To support the old-style scripts
generated by d*/s* in p*, we can use the resource
system.<br><span></span></div></div></blockquote>Not just as is, I believe.
When scripts are installed (as opposed to other resources), it's not enough to
copy them across to the configured destination: you also need to change their
shebang lines to point to the appropriate Python executable. This is
particularly important in virtualenvs where there could be any number of Python
executables (of different versions) represented. But how will we know which .py
files mentioned in resources are data, and which are actually
scripts?<br><br>To me, it actually makes more sense to keep those scripts in
the [scripts] section, and have some way of recognising which scripts need to
be copied/amended and which ones need to be generated from
callables.<br><br></div></div></div></div></body></html>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
