Howdy all, I've received conflicting advice on how to deal with Distribute's eagerness at connecting to the internet during package builds.
On 10-Dec-2012, Barry Warsaw wrote: > Also, please put this near the top of your d/rules file: > > -----snip snip----- > # Prevent setuptools/distribute from accessing the internet. > export http_proxy = http://127.0.9.1:9 > -----snip snip----- > > This should probably be mandatory for any distutils based package. ;) On 11-Oct-2013, Thomas Goirand wrote: > I don't agree with adding: > export http_proxy = http://127.0.9.1:9 > > on top of debian/rules. The reason is that, by doing this, you are hiding > problems. If a python package downloads something using pip or anything > else, it most likely means that you forgot a build-depends. […] > So remove it, and if during the build process something tries to download > a python package, then you need to simply fix your build-depends. > > I'm open to discussions on this very subject though. Thanks to both Barry and Thomas for taking this seriously. Currently I tend to agree with Barry's advice. Successfully downloading a package from the internet during a long package build is hiding dependency problems, and setting the HTTP proxy so that it fails is going to make that problem easier to notice. But, as Thomas says, I'm open to discussions on this. What is the consensus of the Debian Python experts here? -- \ “Intellectual property is to the 21st century what the slave | `\ trade was to the 16th.” —David Mertz | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
