Hi Dammina, No, the breakpoints in theme.py didn't get hit. I added breakpoints for most of the functions. However, the breakpoints in SocketServer.py of Python27 did.
I believe I must missed something here. I am using PyCharm and start it with Run >> Debug 'Bloodhound'. Bloodhound is the project name. Thanks Wenli On Saturday, June 21, 2014 2:45 PM, Dammina Sahabandu <[email protected]> wrote: Hi Wenji, I'm really glad that you have setup the remote debugging environment. However, I'm not very clear what is the issue. So can you put a debug point in ./bloodhound_theme/bhtheme/theme.py and let me know whether it gets hit. Thanks. Dammina On Sat, Jun 21, 2014 at 12:06 PM, Wenli Ji <[email protected]> wrote: Hi Dammina, > >I am able to run Bloodhound in PyCharm now. Thanks for your help. > >I start the standalone.py through debug mode, and set lots of breakpoints in >auth.py. Looks like it's used for login/logout. Then I tried to login from the >homepage, but the breakpoints didn't get triggered? > >Is there something special to debug Bloodhound? > >Thanks >Wenli > > > >On Saturday, June 21, 2014 2:04 PM, Wenli Ji <[email protected]> >wrote: > > > >Hi Dammina, > >Could you give me the complete instruction? I am very new to Python and to >Bloodhound. > >I am struggling with it for two days... You help is very appreciated.. > >Thank you again. > >Wenli >Regards > > > >On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <[email protected]> >wrote: > > > >Hi Wenji, >Unfortunately, I'm not using eclipse for the debugging purpose. I use >JetBrains PyCharm IDE for that. In our mail Archive there is a thread >name "Good >Python IDE" discussing something similar. I hope it would be better for you >to go through it. However, here I have given the instructions extracted >from that thread for setting up PyCharm for remote debugging. > >Checkout the project, create virtual env ... as usual. >Choose Open Directory in PyCharm and locate your bloodhound source. >Go to Preferences / Project Interpreters / Python Interpreters, add a >local interpreter and point it to python executable in bh env. >Create a run configuration like this: > Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py > Script parameters: >/path/to/checkout/bloodhound/installer/bloodhound/environments/main >--port=8000 > Single Instance Only: Yes > >And you are ready to write and debug Bloodhound code :) > >HTH. > >Thanks. >Dammina > > > >On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <[email protected]> >wrote: > >> Hello, >> >> I am able to deploy Bloodhound 0.7 to Apache. However, we need to change >> the code a bit to build a quality system to meet the special requirement. >> >> I didn't find any doc of how to setup the debug environment. I tried to >> follow Trac's doc but didn't make it. I believe there should be something >> different. >> >> Could anyone help? >> >> Thank you very much. >> >> Wenli >> Regards > > > > >-- >Dammina Sahabandu. >Committer for ASF (Apache Bloodhound) >Undergraduate Department of Computer Science and Engineering >University of Moratuwa >Sri Lanka. -- Dammina Sahabandu. Committer for ASF (Apache Bloodhound) Undergraduate Department of Computer Science and Engineering University of Moratuwa Sri Lanka.
