Hi, good news: I have cut a 1.0 release for "bandersnatch", the PEP381 client that I started as an overhaul of "pep381client" at PyCon 2013. Here's the news: * I decided to use a "requirements.txt" to support PIP-based environments.[1] * Markus Zappke Gründemann noticed that I was missing the actual license text and provided me with a pull request. * Overhauled README, hopefully a bit easier to read. * The next step on my agenda is to get all the existing public mirror operators on board so that we hopefully will see more "green bar" moments when visiting pypi-mirrors.org. Who can help? Cheers, Christian [1] There is some integration magic to automatically generate the requirements.txt, have it available for different releases on bitbucket, etc. See "buildout.py" and "release.py" in the package code. Not for the faint of heart. I also added a jenkins job that verifies the requirements.txt, installs the sdist package and runs tests from there.
Gah - my news reader betrayed me while writing this message … On 2013-04-09 20:53:47 +0000, Christian Theune said:
Hi,
good news: I have cut a 1.0 release for "bandersnatch", the PEP381client that I started as an overhaul of "pep381client" at PyCon 2013.
Here's the news:
* I decided to use a "requirements.txt" to support PIP-based environments.[1]
* Markus Zappke Gründemann noticed that I was missing the actuallicense text and provided me with a pull request.
* Overhauled README, hopefully a bit easier to read.
*
This item does not exist. :) Except from that typo I meant to say that I guess that there will be further bugs and I'll be happy to fix them when they get reported. I did see a mirror process getting stuck at some point and I plan to add something to aid debugging those cases. If someone runs into it: just kill it and start it again is sufficient in all cases I encountered while developing it. Cheers, Christian
participants (1)
-
Christian Theune