progrium/ginkgo — pull request #57 by hblanks (2012-04-30 17:12:09+00:00)
Title: use .py for determining if config should be a file, then raise exception...

Currently, when you do:

$ ginkgo path/to/nonexistent/file.py.py

you get the unlikely message:

Starting process with path/to/nonexistent/file.py.py...
usage: ginkgo [-v] [-h] [target]
ginkgo: error: Unable to load class path: path/to/nonexistent/file.py.py:Relative module names not supported

With this pull request, instead you'll get:

Starting process with ./deployment/api.conf.py...
usage: ginkgo [-v] [-h] [target]
ginkgo: error: Configuration file ./deployment/api.conf.py does not exist