Here's what I did (in bash); answers to Mike Orr's questions below.
1. python virtualenv.py --no-site-packages root
2. cd root
3. source bin/activate
4. root/bin/easy_install Pylons
This got me version 0.9.6.2.
5. paster create --template=Pylons Site
6. cd Site
7. paster serve development.ini
On Apr 20, 8:19 am, Mike Orr <[email protected]> wrote:
> Setuptools/pkg_resources is fragile in the sense that the Python path
> can get out of whack in several ways and cause an import error. They
> are all specific to the particular installation environment, so it can
> take some time to track down. It doesn't help that the exception
> doesn't say who's asking for it. The 'config.middleware' could be
> referring to something in Pylons or Paste.
>
> Does it work without the --reload?
Without --reload, it's the same failure.
> What if you recreate the environment (the virtualenv, if you're using it)?
I had an old virtual environment from Feb. 20, so I recreated it
just yesterday.
> Did you install the application before running it? ("python setup.py
> develop"). I'm not sure if it's strictly necessary, but it will
> update the egg-info files, which are what pkg_resources use and can
> cause ImportError if they're not up to date.
I don't recall the book saying to do that, but I did it, and it
worked, but
it didn't help.
> Which OS and Python version are you using? How did you install Pylons?
See above for the install. Base OS is Fedora Core 11.
Best regards,
JohnWShipman <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
