Skip to content
This repository was archived by the owner on Feb 26, 2019. It is now read-only.

add multiple pypi backend#2

Open
cyplp wants to merge 1 commit intocamptocamp:masterfrom
cyplp:master
Open

add multiple pypi backend#2
cyplp wants to merge 1 commit intocamptocamp:masterfrom
cyplp:master

Conversation

@cyplp
Copy link

@cyplp cyplp commented Jun 8, 2012

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.

=========================

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.
@elemoine
Copy link

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.

@cyplp
Copy link
Author

cyplp commented Jun 16, 2012

Maybe I can help to fix them. Do you hav e a list ?

@elemoine
Copy link

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 ALWAYS_REFRESH is True, which is the setting we want to be able to get new versions from the server.

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants