The bug tracker for setuptools 0.7 or higher is on BitBucket

 

Issue28

Title Error message is confusing if you accidentally try to instal a directory
Priority bug Status resolved
Superseder Nosy List ianb@colorstudy.com, pje
Assigned To Keywords

Created on 2008-07-28.01:29:24 by ianb@colorstudy.com, last changed 2008-08-21.17:49:02 by pje.

Messages
msg91 (view) Author: pje Date: 2008-08-21.17:49:02
Fixed in trunk and branch (by making the file/directory name an absolute path in
the error message)
msg63 (view) Author: ianb@colorstudy.com Date: 2008-07-28.01:29:24
I commonly encounter a problem where a person creates a directory with a name,
then tries to install a package with the same name as the directory. 
easy_install then things they were referring to the directory name.  For instance:

  $ mkdir Pylons
  $ mkdir Pylons/src/MyProject # etc...
  $ easy_install Pylons
  Processing Pylons
  error: couldn't find a setup script in Pylons

I think the error message could just be changed, first to make sure the
directory ends with os.path.sep and then saying "error: couldn't find a setup
script in the directory Pylons/" -- with that error message most people would
figure out the problem quickly.
History
Date User Action Args
2008-08-21 17:49:02pjesetstatus: unread -> resolved
nosy: + pje
messages: + msg91
2008-07-28 01:29:24ianb@colorstudy.comcreate