On Jul 1, 2008, at 6:47 AM, Jani Tiainen wrote: > > Alec Thomas kirjoitti: >> This occurs because Trac's static content and templates are shipped >> within the egg. They must be accessible for normal file access and >> thus the egg must be unpacked, or cracked open, if you like. > > I don't get it. > > Wasn't setuptools meant for using simple .egg files (at least most > of my > plugins are in zipfiles, even they contain shared data) and in runtime > setuptools extracts plugins (and staticdata) to some temporary > directory > (egg-cache).
Yes, however this is 1) slower and 2) more likely to result in the famous PYTHON_EGG_CACHE errors. It is tricky to make sure the egg cache variable gets set correctly, as seen by the current issues with zipped eggs and Genshi, so this just side steps the problem for now. If you aren't using mod_python you could probably remove zip_safe=False with no ill effects. > > > So there is something incorrect in above statement. > > Actually now that I look my plugins only EGG that is installed as > extracted is Trac itself for some reason... > > Altough that shouldn't be necessary since to get static resources > out - > user is required to run "deploy" command to extract static data > from .egg. > > Which makes me wonder how system can cope with several trac-admin/ > tracd > scripts... As long as you used differing exec prefixes (so the scripts won't overwrite each other) it will work fine. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
