Changes between Version 6 and Version 7 of TracDev/DevelopmentWithEclipseAndPyDev

Timestamp:

Aug 2, 2008, 8:11:47 PM (16 years ago)

Author:

Piotr Kuczynski <piotr.kuczynski@…>

Comment:

—

TracDev/DevelopmentWithEclipseAndPyDev

@@ -1 @@
-= How to develop Trac with Eclipse PyDev =
+= How to develop Trac with Eclipse !PyDev =
 
-== Installation ==
+== Python Installation ==
 
-Install [http://www.eclipse.org Eclipse] (3.3 or newer will do) and [http://pydev.sourceforge.net PyDev]. Also either [http://subclipse.tigris.org Subclipse] or [http://www.eclipse.org/subversive/ Subversive] is good to have for integrated support to SVN.
+1. Download and install latest [http://www.python.org/download/ Python]
 
-1. Install prerequisities, at least Genshi 
+2. Get easy_install
+Go to [http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install installing-easy-install] and follow the instructions there.  However, most of the time you just take the text at [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py], save it as ez_setup.py on your hard drive, then from the command-line prompt type:
+{{{
+python ez_setup.py
+}}}
+
+3. Install Genshi 
 {{{ 
 $ easy_install genshi 
 }}}
 
-2. You can check out the trac sources inside eclipse using either the subclipse or the subversive plugin.
+== Installing and configuring Trac ==
 
-3. Then build the setuptools info file from the command line 
+=== Downloading trac ===
+From the command-line prompt:
+{{{
+svn co http://svn.edgewall.org/repos/trac/trunk/ trac-trunk
+svn co http://svn.edgewall.org/repos/genshi/trunk/ genshi-trunk
+cd trac-trunk
+python setup.py develop 
+cd ../genshi-trunk
+python setup.py develop
+cd ..
+}}}
+
+=== Setuptools ===
+
+Then build the setuptools info file from the command line 
 {{{
 $ set PYTHONPATH=c:\path\to\your\trac\sources
 $ python setup.py egg_info
-}}}
-
-4. Create a trac environment, e.g. 
-{{{ 
-$ trac-admin /path/to/myproject initenv 
 }}}
 
@@ -31 +46 @@
 }}}
 
-5. In Eclipse, make sure that the PYTHONPATH in the project properties dialog includes the sources for trac.
 
-6. Create an initial run configuration by clicking right on ''trac/web/standalone.py file'', and choosing ''Run As->Python Run''.
+=== Creating your test trac environment ===
+From the command-line prompt:
+{{{
+trac-admin /path/to/myproject initenv
+}}}
+'''note:''' Press return for every option.
+
+== Installing and configuring Eclipse ==
+
+ 1. Install [http://www.eclipse.org Eclipse] (3.3 or newer will do) 
+ 2. Install [http://pydev.sourceforge.net PyDev]
+ 3. Also either [http://subclipse.tigris.org Subclipse] or [http://www.eclipse.org/subversive/ Subversive] is good to have for integrated support to SVN.
+
+ 4. In Eclipse, make sure that the PYTHONPATH in the project properties dialog includes the sources for trac.
+
+ 5. Create an initial run configuration by clicking right on ''trac/web/standalone.py file'', and choosing ''Run As->Python Run''.
 trac will complain that no environment has been set.
 
-7. Select ''Run->Open Run Dialog...'' and set the correct command line arguments in the ''arguments'' tab, eg.
+ 6. Select ''Run->Open Run Dialog...'' and set the correct command line arguments in the ''arguments'' tab, eg.
 ''--port 8000 /path/to/myproject''[[BR]]
 Note that the option --auto-reload will cause tracd to restart every time source code has been changed, but it seems to prevent debugging with pydev. This seems to have something to do way Trac reloads new instance as a child thread using "thread" library which doesn't seem to be compatible with pydev debugging. Googling revelead some hints that instead using "thread"-module you should use "threading"-module (higherlevel)
 
-8. You should now be able to run tracd, as well as to debug it using the same run configuration. To run the test cases, just click on a test folder and select ''Run->Python unit tests''
+ 7. You should now be able to run tracd, as well as to debug it using the same run configuration. To run the test cases, just click on a test folder and select ''Run->Python unit tests''
 
-9. To debug a plugin, deploy it into your test environment via 
+ 8. To debug a plugin, deploy it into your test environment via 
 {{{
 $ python setup.py develop -md /path/to/projenv/plugins
@@ -56 +85 @@
 If you want to setup automatic translation compilation it can be done very easily.
 
-1. Right click on trac project and select ''Properties''. Select ''Builders''. Click ''New''. Select ''Program''.
+ 1. Right click on trac project and select ''Properties''. Select ''Builders''. Click ''New''. Select ''Program''.
 
-2. Name builder, like 'Locale fi_FI builder'
+ 2. Name builder, like 'Locale fi_FI builder'
 
-3. ''Main'' tab: 
+ 3. ''Main'' tab: 
  ''Location'': click ''Browse File System...''. Select Python executable.[[BR]]
  ''Working Directory'': set it to ''${project_loc}''[[BR]]
  ''Arguments'': ''setup.py compile_catalog -f -l fi_FI'' (change to your locale)[[BR]]
 
-4. ''Refresh'' tab:
+ 4. ''Refresh'' tab:
  Check ''Refresh resources upon completion''.[[BR]]
  Select ''Spesific resources'' and select ''trac/locale/fi_FI'' (select your locale)[[BR]]
 
-5. ''Build Options'' tab:
+ 5. ''Build Options'' tab:
  Check ''During auto builds''.[[BR]]
  Check ''Specify working set of relevan resources''.[[BR]]
@@ -75 +104 @@
  Name it like ''fi_FI locale''.[[BR]]
 
-6. After modifying your message.po file you should get following output:
+ 6. After modifying your message.po file you should get following output:
  {{{
   running compile_catalog