Conversation
========================= collective/eggproxy/tests/test_utils.py --------------------------------------- I patched collective/eggproxy/tests/test_utils.py for another egg (the test don't use http://pypi.python.org/simple/ and I don't get it). collective/eggproxy/wsgi.py --------------------------- I patched collective/eggproxy/wsgi.py for split for permit multi index definition : :: index = http://mypypi:8000/simple/ http://pypi.python.org/simple collective/eggproxy/utils.py ---------------------------- I patched for use multiple index. I redifined several functions from setuptool.
|
Thanks for the pull request. We have issues we'd like to fix before introducing new features. I'm hoping we can soon fix these issues and then look at your changes. |
|
Maybe I can help to fix them. Do you hav e a list ? |
|
Thanks for offering to help. We have seen cases where the client (we use buildout) times out because the proxy keeps querying the server (pypi.python.org), even though the proxy already has versions of the requested package. This occurs when At one point I thought this issue triggered when the requested package was no longer available on the server, but up to now I haven't been able to reproduce the issue. So we know we have problems, and they are painful, but we haven't yet clearly identified when the problems occur. @bbinet, please add any additional information you may have. |
add multiple pypi backend
collective/eggproxy/tests/test_utils.py
I patched collective/eggproxy/tests/test_utils.py for another egg (the test don't use http://pypi.python.org/simple/ and I don't get it).
collective/eggproxy/wsgi.py
I patched collective/eggproxy/wsgi.py for split for permit multi index definition :
::
index =
http://mypypi:8000/simple/
http://pypi.python.org/simple
collective/eggproxy/utils.py
I patched for use multiple index. I redifined several functions from setuptool.