On 8 April 2013 06:43, Christian Theune <ct@gocept.com> wrote:
Hi,
I spend some more time on bandersnatch and I'm ready for a stable release, I guess.
Updates ------------
* Add a specific user agent to XML-RPC and plain HTTP calls * Add a specific user agent to the logging to support debugging * Provide a default (10s) network timeout and a config option to customize * Clean up README
PIP ---
I'd be happy to cut a release now. Holger Krekel asked me whether I could ensure that bandersnatch is pip installable. Looking through the PIP documentation I don't see how I can make a simple "pip install bandersnatch" repeatable.
Especially if someone would run a public mirror I would prefer if they would use an installation method that makes their deployment repeatable. From my own experience and background I would prefer buildout in the following style:
$ hg clone https://bitbucket.org/ctheune/bandersnatch $ cd bandersnatch $ hg co 1.0 $ virtualenv-2.7 . $ bin/python bootstrap.py $ bin/buildout $ bin/bandersnatch
Thoughts?
You can make it pip installable without breaking buildout; then folk can choose themselves. Environments that are pip based will have a harder time with more waste if you insist on buildout being the one true way for your tool. -Rob -- Robert Collins <rbtcollins@hp.com> Distinguished Technologist HP Cloud Services