paver nosetests also runs egg_info for no apparent reason...

[ssteiner]

Hi!

I'm kind of new to Paver and I'm using it to automate some build,
test, doc etc. functions.

I'm using nose to do my unit testing so, as an early test of Paver's
functionality, I just gave this simple command a try:

# paver nosetests

For some reason, after running my nose tests just fine, it also
decided to run "egg_info" out of setuptools.command.

Does anyone have any Earthly idea why it would arbitrarily do such a
thing?

My pavement.py file only has brief setup info and no tasks.

pavement.py:

from paver.easy import *
from paver.setuputils import setup

setup(
name='xxx',
version='0.9.0alpha',
description='xxx project',
author='me',
url='http://www.example.com/',
packages=[''mypackage']
)

There is no nose.conf, pretty much nothing that should set Paver off
to run something as obscure as egg_info.

Any clues would be greatly appreciated.

Thanks,

S
aka/Steve Steiner

[ssteiner]

On Sep 9, 9:42 pm, ssteiner <sstein...@gmail.com> wrote:

>   There is no nose.conf, pretty much nothing that should set Paver off
> to run something as obscure as egg_info.

Sorry to have not included this earlier, and for having missed another
thing Paver's doing without any explicit instructions to do so, but
Paver is also running "build_ext."

I've been a little more explicit on the command line about what,
exactly, I want run and have included verbose output so hopefully we
can see what's going on.

egg_info and build_ext are being run unexpectedly.

Here's the Paver output, with nosetests' verbosity set to '2.'

# paver nose.commands.nosetests --verbosity=2
running nosetests
running egg_info
writing cloudservers.egg-info/PKG-INFO
writing top-level names to cloudservers.egg-info/top_level.txt
writing dependency_links to cloudservers.egg-info/dependency_links.txt
reading manifest file 'cloudservers.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'cloudservers.egg-info/SOURCES.txt'
running build_ext
Test JSON conversion of servers with and without metadata. ... ok
Verify that Server properties are readonly. ... ok
Test values of self.server0 ... ok

----------------------------------------------------------------------
Ran 3 tests in 0.035s

OK

Once again, any clues would be greatly appreciated.

[ssteiner]

Adding the @no_auto decorator made the problem go away but I'm still
not satisfied since I don't know the *reason* for those extraneous
functions to have been called in the first place.

S

[Kevin Dangoor]

Wow. That's weird. Unless you have a task in your pavement called "auto", I don't think no_auto should do anything at all.

From the output you provided, it didn't look like paver was running egg_info and build_ext, because I believe paver puts a --> before the names of tasks that it's running. I think it's something in the distutils/setuptools machinery that is running those things (making a no_auto connection that much harder to imagine)

Kevin


--
Kevin Dangoor

work: http://labs.mozilla.com/
email: k...@blazingthings.com
blog: http://www.BlueSkyOnMars.com

[jhermann]

That build_ext is called for tests is not surprising at all -- if you
have extension modules, they're needed for the tests after all.
Similarly, egg_info writes important metadata that your tests COULD
need (setuptools doesn't know, so it assumes "yes, you do").