Github recently changed their API so that authentication details added to public repos, even though they're public, will still 401 if the details aren't correct.
Some projects use Github downloads (either static or auto-tarball based) as their canonical URLs, with no PyPi hosted version of the egg either, which has started breaking our builds (one of the high profile examples of this is bit.ly's asyncmongo MongoDB library for Tornado) as lovely.builtouthttp adds auth details to all Github URLs.
To get around this I've added a completely optional buildout.github-repos config option that takes a list of repos in the form <gituser>/<repos> and whitelists these URLs for auth details but otherwise skips them.
Github recently changed their API so that authentication details added to public repos, even though they're public, will still 401 if the details aren't correct.
Some projects use Github downloads (either static or auto-tarball based) as their canonical URLs, with no PyPi hosted version of the egg either, which has started breaking our builds (one of the high profile examples of this is bit.ly's asyncmongo MongoDB library for Tornado) as lovely.builtouthttp adds auth details to all Github URLs.
To get around this I've added a completely optional
buildout.github-repos
config option that takes a list of repos in the form<gituser>/<repos>
and whitelists these URLs for auth details but otherwise skips them.