[issue976869] Stripping script extensions with distutils

Éric Araujo added the comment: We’re going to follow setuptools’ lead and generate platform-appropriate script or binary files from callables. -- resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder: -> packaging: generate scripts from

[issue976869] Stripping script extensions with distutils

Fred L. Drake, Jr. added the comment: At this point, I'm more in favor of adopting something closer to the setuptools scripts based on "console_scripts" entry points, and dropping old-style scripts entirely (most *because* of the issues I mentioned at the start). -- _

[issue976869] Stripping script extensions with distutils

Éric Araujo added the comment: Akira: Why require people to manually run this command instead of bundling it into distutils? After all, install_scripts is just a cp, but distutils still does it :) I wonder if this should be a built-in functionality like in Fred’s patch or an install hook sh

[issue976869] Stripping script extensions with distutils

Changes by Tarek Ziadé : -- components: +Distutils2 -Distutils ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue976869] Stripping script extensions with distutils

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue976869] Stripping script extensions with distutils

Tarek Ziadé added the comment: It makes sense to me but we need to look at setuptools console feature nowadays. I think it might be the right piece to add in distutils for console scripts. -- assignee: -> tarek ___ Python tracker

[issue976869] Stripping script extensions with distutils

Akira Kitada added the comment: I doubt "strip-extensions" has to be in distutils. Isn't a simple script like below enough for this? $ for i in *.py; do mv $i ${i%.py}; done -- nosy: +akitada, tarek ___ Python tracker