Bryan Kadzban wrote:
> However, I
> don't think it will look in root's home directory for the file; I think
> it only looks in /usr/lib/python2.4{,/site-packages} and subdirectories.
Good point.
> (That's where I found the .egg file referred to earlier, which contains
> the web_ui.py that's broken.)
> This is a complete and utter guess, but I would *suspect* that
> /root/accountmanagerplugin was an extracted version of
> /root/accountmanagerplugin-trunk.zip (likely an SVN snapshot from around
> Dec 4); /root/accountmanager seems to be a checkout of the SVN repo
> where it's actually stored. The TracAccountManager-<version>.egg files
> in the same directory are probably the built versions.
>
> Based on this, I would *suspect* that you'd have to modify
> /root/accountmanager/acct_mgr/web_ui.py, then (somehow) rebuild the .egg
> file, then copy it to /usr/lib/python2.4/site-packages/<wherever> again.
> Maybe do some easy_installer stuff as well, I'm unsure.
An egg is only a zip file with a different extension. I think that these files
are extracted to a cache and run from there, but I don't know how a new file
could be recognized.
I do have a reasonably extensive reference library -- digging out my book on
Python...
It appears that a .pyc file is automatically generated the first time a .py
file
is run so, strictly speaking, you don't need to include the .pyc file.
From the web:
".egg files are a "zero installation" format for a Python package; no build or
install step is required, just put them on PYTHONPATH or sys.path and use them
(may require the runtime installed if C extensions or data files are used)"
The httpd conf file has:
PythonOption TracEnv /srv/trac/LFS
PythonOption TracUriRoot /lfs
setEnv PYTHON_EGG_CACHE /srv/trac/LFS/cache
but the cache file doesn't have any .py or .pyc files.
I'll try to take a further look in the next couple of days.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
