Just to follow up on this issue- instead of dealing with the eggs cache permissions issue that caused this, I've found it's easy enough to avoid it altogether by using pip instead of easy_install when installing pyamf.
$ pip install pyamf INSTEAD OF $ easy_install pyamf pip by default does not use eggs/zip files, and it gave me a clean install that ran with no problems. Mabye the pyamf section of the book should recommend this? (http://web2py.com/book/default/section/ 9/2) On Jun 21, 2:26 am, mdipierro <[email protected]> wrote: > On Jun 20, 8:50 pm,Yarin<[email protected]> wrote: > > > I set up web2py on a Fedora EC2 server, running with mod_wsgi and > > Apache. Everything was working great with the initial setup. I then > > tried to get amf working, by doing the following: > > > $ easy_install pyamf > > $ apachectl restart > > > However, when I try to connect with my Flex client, I get: > > "pyamf not installed or not in Python sys.path" > > > When I run web2py from the command line and check sys.path, I see > > '/usr/lib/python2.5/site-packages/PyAMF-0.5.1-py2.5-linux-i686.egg' > > > Is restarting Apache not enough? Do RPC services even run through > > Apache? (excuse my ignorance) > > It should. Is it possible you have different versions of Python? > > > > > > > Thanks-Yarin
