On Mon, Apr 4, 2011 at 9:14 AM, "Martin v. Löwis" wrote:
>> That sounds awesome, especially for testing tools that have to interact
>> with pypi.
>
> Actually, for testing tools, I think the requirements are quite
> different: you want concurrent runs of the same test case on multiple
> machines,
On 04/04/2011 00:14, "Martin v. Löwis" wrote:
That sounds awesome, especially for testing tools that have to interact
with pypi.
Actually, for testing tools, I think the requirements are quite
different: you want concurrent runs of the same test case on multiple
machines, so you need to make sur
> That sounds awesome, especially for testing tools that have to interact
> with pypi.
Actually, for testing tools, I think the requirements are quite
different: you want concurrent runs of the same test case on multiple
machines, so you need to make sure they don't collide.
So for that use case,
On 01/04/2011 23:39, Richard Jones wrote:
Hi all,
How about we set up a second instance of PyPI on dev.pypi.python.org.
It will have a completely separate database (except for users) and
package/docs store. We'd want the user list to be identical or there
could be problems. Having the dev syste
Hi all,
How about we set up a second instance of PyPI on dev.pypi.python.org.
It will have a completely separate database (except for users) and
package/docs store. We'd want the user list to be identical or there
could be problems. Having the dev system use the primary system's user
database mig
