surprise dependency of python?

[gopherbot]

by schwehr:

a reference to python runtime-gdb.py exists inside of go binaries without reference to
which interpreter

Many machines have lots of python binaries... e.g. my mac has a system python 2.7, fink
provides python 2.7/3.1./3.2/3.3, and so do homebrew, macports and lots of other ways
exist to have python.  There is no way to obvious control which python.  There is no
mention of the use of python in install-source.html.

find . -type f | xargs grep python
./doc/devel/weekly.html:* misc/dashboard: remove old python package dashboard.
./doc/devel/weekly.html:* dashboard: remove old python/bash builder, update README.
./doc/devel/weekly.html:* misc: update python scripts to specify python2 as python3 is
now "python".
./src/cmd/ld/dwarf.c:   // TODO(lvd) fix gdb/python to load MachO (16 char section name
limit)
./src/pkg/runtime/runtime-gdb.py:# fields to python attributes in gdb.py isn't complete:
you can't test

[adg]

Comment 1:

Like I said in the other issue, Python is not a dependency the Go tool chain.
There is a gdb extension written in Python that is useful for people using versions of
gdb earlier than 7.5. At gdb 7.5 and above, gdb provides native go language support.

Status changed to Invalid.

[gopherbot]

Comment 2 by schwehr:

WTF?  You have unstated python in your package (wrt to the install documentation and
scripts).  That python file should state exactly what you just wrote and let the
packagers evaluate if we need to include that python.  And state it again in the install
directions.  My binary hello world built with a reference to a python file, so you have
a dependency on python (or code you should delete).
How in the world is my issue invalid?

[minux]

Comment 3:

The reference to python is in the __DWARF.__debug_gdb_scri(pt) section, which
is only meant for gdb.
And in case it's not apparent, you don't install python for that, if you insist, you
need to install gdb with python 2 binding (I doubt fink Go package will depends
on gdb with python 2 binding).
Also, that script has nothing to do with executing Go programs or running Go
toolchain.
Your issue is invalid because Go binaries don't in any way depend on Python.

[adg]

Comment 4:

Filed issue #6963 to ask some of the questions raised here.