[tor-bugs] #10847 [Flashproxy]: "setup-common.py" test fetches dependencies

[Tor Bug Tracker & Wiki]

#10847: "setup-common.py" test fetches dependencies
------------------------+---------------------
 Reporter:  dcf         |          Owner:  dcf
     Type:  defect      |         Status:  new
 Priority:  normal      |      Milestone:
Component:  Flashproxy  |        Version:
 Keywords:              |  Actual Points:
Parent ID:              |         Points:
------------------------+---------------------
 `make test` or `python setup-common.py test` attempts to download and
 build M2Crypto if you don't already have it installed.
 {{{
 ~/flashproxy$ python setup-common.py test
 running test
 Searching for M2Crypto
 Reading https://pypi.python.org/simple/M2Crypto/
 Best match: M2Crypto 0.22.3
 Downloading
 https://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.22.3.tar.gz#md5=573f21aaac7d5c9549798e72ffcefedd
 Processing M2Crypto-0.22.3.tar.gz
 Writing /tmp/easy_install-JYaMle/M2Crypto-0.22.3/setup.cfg
 Running M2Crypto-0.22.3/setup.py -q bdist_egg --dist-dir /tmp
 /easy_install-JYaMle/M2Crypto-0.22.3/egg-dist-tmp-W0yfDL
 unable to execute swig: No such file or directory
 error: Setup script exited with error: command 'swig' failed with exit
 status 1
 }}}
 At least, we need to disable this network fetching somehow. From previous
 experience I learned that there's no way to prevent setuptools from
 automatically downloading packages. You can fake it out, however, by
 setting the `http_proxy` and `https_proxy` environment variables, which is
 what they do in Debian packages.
  * https://gitweb.torproject.org/pluggable-
 transports/bundle.git/commit/e2632d9a52e41fbb359534c87b16c591437a6f45
  * https://wiki.debian.org/Python/LibraryStyleGuide
 Another possible alternative is to run the tests in a way that doesn't go
 through setuptools.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10847>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online