Binary nose and flake8 packages not properly registering the distutils entry point.

[mforbes]

Currently, the nose-1.3.4-py27_0 package contains lib/python2.7/site-packages/nose-1.3.4-py2.7.egg-info rather than the directory lib/python2.7/site-packages/nose-1.3.4.dist-info installed by pip install nose. This somehow does not properly register the distutils nosetest entry-point, breaking python setup.py nosetests as described in this nose issue.

I'm not sure exactly what the problem is, but it would probably be solved by rebuilding the current package with a recent version of pip or setuptools.

This is also an issues with the flake8 package for which python setup.py flake8 fails with the binary installation of flake8.

(migrated from conda/conda#1183)

[letmaik]

I have a similar problem. On a fresh conda create --yes -n test python=2.7.9 there is no nose installed, and when pip installes the missing nose (note I use a mix of conda and pip installing) then everything is fine. However, with conda create --yes -n test python=3.4.2 there seems to be already a corrupt nose version installed by default, so pip says it is already there and subsequently the tests fail because the nosetests entry-point is not correctly registered.

This is new, it didn't happen one or two weeks ago.

[letmaik]

Still broken.

[mforbes]

Squeak! This is really annoying and should be a pretty simple fix. If this is not the right place to reference these types of issues, please let me know where I can submit a patch or the appropriate issue.

[acourdavault]

Still broken today, is there any workaround known?

[letmaik]

@acourdavault Do pip install -U nose to force a re-install from pypi...