This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author theaney
Recipients
Date 2006-06-06.11:19:14
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=827666


I'm not sure I know how. It looks like the downloaded files
have the following shebang lines

  Tools/scripts/pydoc   => #!/usr/bin/env python
  Tools/scripts/idle    => #! /usr/bin/env python
  Lib/smtpd.py          => #! /usr/bin/env python
  Misc/python-config.in => #!@BINDIR@/python

whereas the installed files have

  /usr/local/bin/pydoc         => #!/usr/local/bin/python
  /usr/local/bin/idle          => #!/usr/local/bin/python
  /usr/local/bin/smtpd.py      => #!/usr/local/bin/python
  /usr/local/bin/python-config => #!/usr/local/bin/python

so they're already getting rewritten somewhere. We want both
their names and their shebang lines to have the version

  /usr/local/bin/pydoc2.5          => #!/usr/local/bin/python2.5
  /usr/local/bin/idle2.5           => #!/usr/local/bin/python2.5
  /usr/local/bin/smtpd.py2.5       => #!/usr/local/bin/python2.5
  /usr/local/bin/python-config2.5  => #!/usr/local/bin/python2.5

It seems that python-config appears in the Makefile, so
adding something like

	sed -e "s,@BINDIR@,$(BINDIR)," <
$(srcdir)/Misc/python-config.in >python-config$(VERSION)$(EXE)
	$(INSTALL_SCRIPT) python-config
$(BINDIR)/python-config$(VERSION)$(EXE)
	rm python-config

to Makefile.pre.in in an altlibainstall section or something
might be all we need for that.

The others are named in setup.py

          # Scripts to install
          scripts = ['Tools/scripts/pydoc',
'Tools/scripts/idle',
                     'Lib/smtpd.py']

but I haven't worked out where they get rewritten or
installed yet.


History
Date User Action Args
2008-01-20 09:58:43adminlinkissue1495488 messages
2008-01-20 09:58:43admincreate