Ok, bit of log I get when I want to connect from tracViewer. ==================================================================================== 2012-03-12 10:07:07,967 Trac[session] DEBUG: Retrieving session for ID 'klm' 2012-03-12 10:07:07,967 Trac[chrome] DEBUG: Prepare chrome data for request 2012-03-12 10:10:48,692 Trac[main] DEBUG: Dispatching <Request "GET u'/admin/ticket/versions'"> 2012-03-12 10:10:48,693 Trac[cache] DEBUG: cache metadata undefined (youngest_rev=u'') 2012-03-12 10:10:48,693 Trac[cache] INFO: repos rev [0] != cached rev [None] 2012-03-12 10:10:48,694 Trac[chrome] DEBUG: Prepare chrome data for request 2012-03-12 10:10:48,697 Trac[session] DEBUG: Retrieving session for ID 'klm' 2012-03-12 10:10:49,037 Trac[main] DEBUG: Dispatching <Request "GET u'/chrome/site/your_project_logo.png'"> 2012-03-12 10:10:49,038 Trac[session] DEBUG: Retrieving session for ID 'klm' 2012-03-12 10:10:49,038 Trac[chrome] DEBUG: Prepare chrome data for request 2012-03-12 10:10:54,028 Trac[main] DEBUG: Dispatching <Request "GET u'/admin/ticket/type'"> ====================================================================================
I installed the plugin according to instructions in trac-hacks. I don't have the 'problem' with the PYTHONPATH any more I modified trac.ini file with components section. Anything obvious? Kamil On Mon, Mar 12, 2012 at 4:10 PM, osimons <[email protected]> wrote: > > On Monday, March 12, 2012 11:46:03 AM UTC+1, Kamil wrote:My questions: > >> 1. What is that PYTHONPATH variable? To which value it has to be switch >> set? >> > > If you have virtualenv installed, and have activated it (either by > "activate" or by running configured scripts directly like > "/path/to/env/bin/easy_install") all environment settings should be > prepared for you. You should just use the defaults for the virtualenv and > don't need additional paths, so really just ignore it. The modules you > install for the virtualenv will end up in > /path/to/env/lib/python2.x/site-packages/ which is just fine, and don't use > additional configuration or command-line switches when installing. > > >> 2. What is that source /path/to/env/bin/activate command for? >> > > See 1. It basically switches your shell to environment variables prepared > for the virtualenv you activate. So that you run the correct scripts, > install to correct locations etc. You may want to read through the > virtualenv docs and make sure you understand what virtualenv is (and > isn't): http://pypi.python.org/pypi/virtualenv > > >> 3. If I install this in my Python/Trac environment will the plugin be >> available to all my trac sites automatically? >> > > Yes, it will be a "global" install - for all trac processes that originate > in that virtualenv. Need to be enabled in each project. > > >> 4. Where to observe the log if any? >> > > http://trac.edgewall.org/wiki/TracLogging > > > :::simon > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/trac-users/-/jmGuKdyZsIYJ. > > 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-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en.
