On 04/04/2011 03:01, Richard Jones wrote:
On Mon, Apr 4, 2011 at 9:14 AM, "Martin v. Löwis"<mar...@v.loewis.de> 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 sure they don't collide.
So for that use case, I rather suggest to setup an installation that
allows dynamic creation of PyPI instances, each one good for only an
hour. Their URLs would be test.pypi.python.org/<generatedid>.
I believe such tests should be run against a mocked PyPI so the test
has complete control over responses and error cases.
For integration level tests running against a mocked server is fine.
However if pypi behaviour changes your mocks won't reflect that, so your
tests could be passing but your code broken. For functional level tests
you ideally want to run against a *real* implementation of pypi -
preferably local (and under your control) but having a dev server to run
against would be the next best thing.
All the best,
Michael
I believe there's general agreement that a dev.pypi.python.org is a
good idea. We just need to figure out the details. I'll take the
technical discussion offline with Martin unless there's any
objections? No, I'm not writing a PEP for it (unless someone from the
PSF Infrastructure Committee requires it).
Richard
_______________________________________________
pydotorg-www mailing list
pydotorg-www@python.org
http://mail.python.org/mailman/listinfo/pydotorg-www
--
http://www.voidspace.org.uk/
May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html
_______________________________________________
pydotorg-www mailing list
pydotorg-www@python.org
http://mail.python.org/mailman/listinfo/pydotorg-www
