Here is a rough draft proposal for declaring tests in eggs:
Introduction
Software packages should have automated tests. Consumers of
packages will often want to run these tests. Tools should be able to
do this automatically. This proposal seeks to provide a way for
automated
Thanks for the reply, but I don't really understand your response. I don't
know why multiple packages would install the same __init__.py file. I think
that would be an error to do so on my part as a packager. Maybe I am
missing the point.
Here is some more info. Maybe this enough to show
At 09:05 AM 1/5/2007 -0500, Kurt Schwehr wrote:
Here is what the pth looks like. Is there something wrong with it then?
cat /sw/lib/python2.5/site-packages/dap-2.2.5.7-py2.5-nspkg.pth
import sys,new,os; p = os.path.join(sys._getframe(1).f_locals['sitedir'],
*('dap', 'plugins')); ie =
David Fraser wrote:
Jim Fulton wrote:
Here is a rough draft proposal for declaring tests in eggs:
Introduction
Software packages should have automated tests. Consumers of
packages will often want to run these tests. Tools should be able to
do this automatically. This
At 08:46 AM 1/5/2007 -0500, Jim Fulton wrote:
Here is a rough draft proposal for declaring tests in eggs:
Introduction
Software packages should have automated tests. Consumers of
packages will often want to run these tests. Tools should be able to
do this automatically. This
At 01:11 PM 1/5/2007 -0500, Jim Fulton wrote:
Phillip J. Eby wrote:
...
Why can't an entry point invoke a test loader itself?
This seems much simpler and more straightforward to me.
Because that requires you to write code for something that can adequately
be expressed through an existing
I've now fixed the bug below in both the 0.6 branch and the development
trunk. You can get them by easy_installing either 'setuptools==dev06' or
'setuptools==dev', respectively.
At 11:43 AM 1/5/2007 -0500, Phillip J. Eby wrote:
At 09:05 AM 1/5/2007 -0500, Kurt Schwehr wrote:
If I read that
I'm trying to create a package that provides a setuptool command that will
compile idl files when you run python setup.py build or python setup.pyinstall.
I've figured out how to add an additional command (build_omniidl) which I
can run with:
python setup.py build_omniidl
But I'm not sure how
