My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Last 7 days

  • Dec 30, 2009
    issue 4 (Ctrl-U at debugger prompt removes prompt) reported by Matthew.C.Snyder   -   What steps will reproduce the problem? 1. Insert debugger into program using the API import and a call to debug() 2. Execute program and reach debugger prompt 3. Type a command, but before hitting Enter, type Ctrl-U. What is the expected output? What do you see instead? Input should be cleared up to the prompt, but instead removes the prompt as well, reducing the output buffer to an empty line. What version of the product are you using? On what operating system? The latest version available through easy_install.
    What steps will reproduce the problem? 1. Insert debugger into program using the API import and a call to debug() 2. Execute program and reach debugger prompt 3. Type a command, but before hitting Enter, type Ctrl-U. What is the expected output? What do you see instead? Input should be cleared up to the prompt, but instead removes the prompt as well, reducing the output buffer to an empty line. What version of the product are you using? On what operating system? The latest version available through easy_install.

Last 30 days

  • Dec 24, 2009
    issue 3 (request for tarball release) Status changed by rocky.bernstein   -   Release 0.1.3 of pydbgr has been released along with an update of one of the packages it uses pytracer (0.2.3). Note that in addition to pytracer, this package requires Python packages columnize, coverage and import_relative. Happy Packaging!
    Status: Fixed
    Release 0.1.3 of pydbgr has been released along with an update of one of the packages it uses pytracer (0.2.3). Note that in addition to pytracer, this package requires Python packages columnize, coverage and import_relative. Happy Packaging!
    Status: Fixed
  • Dec 24, 2009
    pydbgr-0.1.3.tar.gz (Release 0.1.3 source tarball) file uploaded by rocky.bernstein   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Dec 24, 2009
    pydbgr-0.1.3-py2.6.egg (Release 0.1.3 egg for Python 2.6) file uploaded by rocky.bernstein   -  
    Labels: Featured Type-Package OpSys-All
    Labels: Featured Type-Package OpSys-All
  • Dec 24, 2009
    pydbgr-0.1.3-py2.5.egg (Release 0.1.3 egg for Python 2.5) file uploaded by rocky.bernstein   -  
    Labels: Featured Type-Package OpSys-All
    Labels: Featured Type-Package OpSys-All
  • Dec 24, 2009
    r173 (Release branch 0.1.3) committed by rocky.bernstein   -   Release branch 0.1.3
    Release branch 0.1.3
  • Dec 24, 2009
    r172 (Update NEWS before release) committed by rocky.bernstein   -   Update NEWS before release
    Update NEWS before release
  • Dec 24, 2009
    r171 (For emacs support see http://github.com/rocky/emacs-dbgr ) committed by rocky.bernstein   -   For emacs support see http://github.com/rocky/emacs-dbgr
    For emacs support see http://github.com/rocky/emacs-dbgr
  • Dec 24, 2009
    r170 (Get ready for 0.1.3 release ) committed by rocky.bernstein   -   Get ready for 0.1.3 release
    Get ready for 0.1.3 release
  • Dec 23, 2009
    r169 (Tagged wrong release yet again. ) committed by rocky.bernstein   -   Tagged wrong release yet again.
    Tagged wrong release yet again.
  • Dec 23, 2009
    r168 (Tagging last release properly. Thanks to YY for noticing and...) committed by rocky.bernstein   -   Tagging last release properly. Thanks to YY for noticing and caring.
    Tagging last release properly. Thanks to YY for noticing and caring.
  • Dec 23, 2009
    r167 (Tagged wrong location. ) committed by rocky.bernstein   -   Tagged wrong location.
    Tagged wrong location.
  • Dec 23, 2009
    r166 (Tagged wrong location. ) committed by rocky.bernstein   -   Tagged wrong location.
    Tagged wrong location.
  • Dec 23, 2009
    r165 (Tagging 1.1.2 release. Thanks to YY for noticing and caring....) committed by rocky.bernstein   -   Tagging 1.1.2 release. Thanks to YY for noticing and caring.
    Tagging 1.1.2 release. Thanks to YY for noticing and caring.
  • Dec 23, 2009
    r164 (Tag the last release. Thanks again to YY for caring. ) committed by rocky.bernstein   -   Tag the last release. Thanks again to YY for caring.
    Tag the last release. Thanks again to YY for caring.
  • Dec 21, 2009
    DesignThoughtsAndIssuesEncountered (Random Thoughts on the Rewrite) Wiki page edited by rocky.bernstein   -   Revision r163 Grammar typo.
    Revision r163 Grammar typo.
  • Dec 21, 2009
    issue 3 (request for tarball release) commented on by rocky.bernstein   -   Ok. Will try to have something for in the Christmas - New Year range.
    Ok. Will try to have something for in the Christmas - New Year range.
  • Dec 08, 2009
    issue 3 (request for tarball release) reported by rakesh.pandit   -   Hello Rocky, Thanks for your nice work here. I was planning to package this for fedora. It would be great if you can do a tarball (bz2 or gz) release for 0.1.2 ? -- Regards, Rakesh Pandit Fedora Package Maintainer
    Hello Rocky, Thanks for your nice work here. I was planning to package this for fedora. It would be great if you can do a tarball (bz2 or gz) release for 0.1.2 ? -- Regards, Rakesh Pandit Fedora Package Maintainer
  • Dec 06, 2009
    DesignThoughtsAndIssuesEncountered (Random Thoughts on the Rewrite) Wiki page edited by rocky.bernstein   -   Revision r162 Edited wiki page through web user interface.
    Revision r162 Edited wiki page through web user interface.

Older

  • Nov 28, 2009
    issue 2 (Start pydbgr and press return twice) Owner changed by rocky.bernstein   -  
    Owner: rocky.bernstein
    Owner: rocky.bernstein
  • Nov 28, 2009
    issue 2 (Start pydbgr and press return twice) Status changed by rocky.bernstein   -   Thanks for the report. This problem and a couple of other problems related to running pydbgr without a script name should be fixed in svn. Is running a debugger without a script name is something that is normally done? I've always thought of it as a little bit of an edge-case which is one reason support for it is a little bit flaky.
    Status: Fixed
    Thanks for the report. This problem and a couple of other problems related to running pydbgr without a script name should be fixed in svn. Is running a debugger without a script name is something that is normally done? I've always thought of it as a little bit of an edge-case which is one reason support for it is a little bit flaky.
    Status: Fixed
  • Nov 28, 2009
    r161 (Numerous small bugs including issue #2. cmdproc.py: fix sma...) committed by rocky.bernstein   -   Numerous small bugs including issue #2 . cmdproc.py: fix small bugs when no script name given source.py: we shouldn't need a script name to source a file. finish.py: remove debug print base_cmd.py: Cope with EOF on message printing test-noscript.py: test issuing pydbgr without giving a script name. (This test is not very good or complete). helper.py: allow passing no script. Remove debug print
    Numerous small bugs including issue #2 . cmdproc.py: fix small bugs when no script name given source.py: we shouldn't need a script name to source a file. finish.py: remove debug print base_cmd.py: Cope with EOF on message printing test-noscript.py: test issuing pydbgr without giving a script name. (This test is not very good or complete). helper.py: allow passing no script. Remove debug print
  • Nov 25, 2009
    issue 2 (Start pydbgr and press return twice) reported by rodseth   -   What steps will reproduce the problem? 1. Install pydbgr 2. Start pydbgr 3. Press return twice What is the expected output? What do you see instead? Expected blank new lines. This is what I got: (Pydbgr) Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable Uncaught exception. Entering post-mortem debugger... (/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py:611): process_command !! 611 if last_command[0] == '#': (Pydbgr:pm) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 67, in post_mortem_excepthook post_mortem((exc_type, exc_value, exc_tb)) File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 142, in post_mortem dbg.core.processor.event_processor(f, 'exception', exc, 'Pydbgr:pm') File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 310, in event_processor self.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable Original exception was: Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable What version of the product are you using? On what operating system? pydbgr --version gives: pydbgr version 0.1.0 I'm using Arch Linux, fully updated, on a 64-bit computer. My version of Python is: Python 2.6.4 Please provide any additional information below. I understand that pydbgr is under heavy development.
    What steps will reproduce the problem? 1. Install pydbgr 2. Start pydbgr 3. Press return twice What is the expected output? What do you see instead? Expected blank new lines. This is what I got: (Pydbgr) Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable Uncaught exception. Entering post-mortem debugger... (/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py:611): process_command !! 611 if last_command[0] == '#': (Pydbgr:pm) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 67, in post_mortem_excepthook post_mortem((exc_type, exc_value, exc_tb)) File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 142, in post_mortem dbg.core.processor.event_processor(f, 'exception', exc, 'Pydbgr:pm') File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 310, in event_processor self.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable Original exception was: Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable What version of the product are you using? On what operating system? pydbgr --version gives: pydbgr version 0.1.0 I'm using Arch Linux, fully updated, on a 64-bit computer. My version of Python is: Python 2.6.4 Please provide any additional information below. I understand that pydbgr is under heavy development.
  • Nov 09, 2009
    DesignThoughtsAndIssuesEncountered (Random Thoughts on the Rewrite) Wiki page commented on by OlegOAndreev   -   > But in truth, I also get so few comments about pydb that it's just as likely that no on uses it. I must say, the lack of comments is IMHO due to the fact, that pydb just works (tm), so there is nothing to say about this great application really :)
    > But in truth, I also get so few comments about pydb that it's just as likely that no on uses it. I must say, the lack of comments is IMHO due to the fact, that pydb just works (tm), so there is nothing to say about this great application really :)
  • Nov 05, 2009
    r160 (Canonical filenames when adding breakpoints. ) committed by rocky.bernstein   -   Canonical filenames when adding breakpoints.
    Canonical filenames when adding breakpoints.
  • Nov 05, 2009
    r159 (Use bp.icon_char) committed by rocky.bernstein   -   Use bp.icon_char
    Use bp.icon_char
  • Nov 05, 2009
    r158 (Fix bugs in icon_char. ) committed by rocky.bernstein   -   Fix bugs in icon_char.
    Fix bugs in icon_char.
  • Nov 05, 2009
    r157 (Add icon_char - one-character icon state for a brkpt) committed by rocky.bernstein   -   Add icon_char - one-character icon state for a brkpt
    Add icon_char - one-character icon state for a brkpt
  • Nov 05, 2009
    r156 (Small docstring correction) committed by rocky.bernstein   -   Small docstring correction
    Small docstring correction
  • Nov 05, 2009
    r155 (Fix status indicator in list command to show current locatio...) committed by rocky.bernstein   -   Fix status indicator in list command to show current location, breakpoints, and possibly the breakpoint number.
    Fix status indicator in list command to show current location, breakpoints, and possibly the breakpoint number.
  • Oct 30, 2009
    r154 (Off by one bug in finish. But is the only thing wrong? ) committed by rocky.bernstein   -   Off by one bug in finish. But is the only thing wrong?
    Off by one bug in finish. But is the only thing wrong?
  • Oct 26, 2009
    pydbgr-0.1.2-py2.6.egg (Release 0.1.2 egg for Python 2.6 ) file uploaded by rocky.bernstein   -  
    Labels: Featured OpSys-All
    Labels: Featured OpSys-All
  • Oct 26, 2009
    pydbgr-0.1.2-py2.5.egg (Release 0.1.1 egg for Python 2.5) file uploaded by rocky.bernstein   -  
    Labels: Featured OpSys-All
    Labels: Featured OpSys-All
  • Oct 26, 2009
    r153 (Release branch 0.1.2) committed by rocky.bernstein   -   Release branch 0.1.2
    Release branch 0.1.2
  • Oct 26, 2009
    r152 (Last update before release 0.1.2 ) committed by rocky.bernstein   -   Last update before release 0.1.2
    Last update before release 0.1.2
  • Oct 22, 2009
    r151 (Update what's up in preparation for release. ) committed by rocky.bernstein   -   Update what's up in preparation for release.
    Update what's up in preparation for release.
  • Oct 19, 2009
    r150 (When we are stopped at a breakpoint, make that the event. ) committed by rocky.bernstein   -   When we are stopped at a breakpoint, make that the event.
    When we are stopped at a breakpoint, make that the event.
  • Oct 18, 2009
    r149 (info file xx lines -> info file xx brkpts ) committed by rocky.bernstein   -   info file xx lines -> info file xx brkpts
    info file xx lines -> info file xx brkpts
  • Oct 17, 2009
    r148 (Docstring correction) committed by rocky.bernstein   -   Docstring correction
    Docstring correction
  • Oct 17, 2009
    r147 (Missed a couple of places where traceset -> events Allow sho...) committed by rocky.bernstein   -   Missed a couple of places where traceset -> events Allow showing commands which matching a regular expression.
    Missed a couple of places where traceset -> events Allow showing commands which matching a regular expression.
  • Oct 16, 2009
    r146 (cli.py: allow entry without a Python program to debug. trace...) committed by rocky.bernstein   -   cli.py: allow entry without a Python program to debug. trace.py, default.py: traceset -> events exit.py: we don't need to have a stack to run exit
    cli.py: allow entry without a Python program to debug. trace.py, default.py: traceset -> events exit.py: we don't need to have a stack to run exit
  • Oct 15, 2009
    r145 (Go over doc string for debug(). Thanks to Yarik yet again, f...) committed by rocky.bernstein   -   Go over doc string for debug(). Thanks to Yarik yet again, for reminding me how bad my English skills are.
    Go over doc string for debug(). Thanks to Yarik yet again, for reminding me how bad my English skills are.
  • Oct 15, 2009
    Tutorial (Installing and Using pydbgr) Wiki page edited by rocky.bernstein   -   Revision r144 change debug() parameter "step" to "step_ignore". Thanks to Yaroslav Halchenko for reporting the problem' .
    Revision r144 change debug() parameter "step" to "step_ignore". Thanks to Yaroslav Halchenko for reporting the problem' .
  • Oct 15, 2009
    r143 (api.py: debug() change parameter "step" to "step_ignore". Th...) committed by rocky.bernstein   -   api.py: debug() change parameter "step" to "step_ignore". Thanks to Yaroslav Halchenko for reporting the problem' . test-help.py: test_help_categories() add tests for recent bugs
    api.py: debug() change parameter "step" to "step_ignore". Thanks to Yaroslav Halchenko for reporting the problem' . test-help.py: test_help_categories() add tests for recent bugs
  • Oct 15, 2009
    Tutorial (Installing and Using pydbgr) Wiki page edited by rocky.bernstein   -   Revision r142 First pydbgr.api import example typo fixed. Thanks to Yaroslav Halchenko for reporting the problem
    Revision r142 First pydbgr.api import example typo fixed. Thanks to Yaroslav Halchenko for reporting the problem
  • Oct 15, 2009
    r141 (Fix bug in listing command categories with *. Thanks to Yaro...) committed by rocky.bernstein   -   Fix bug in listing command categories with *. Thanks to Yaroslav Halchenko for reporting the problem
    Fix bug in listing command categories with *. Thanks to Yaroslav Halchenko for reporting the problem
  • Oct 15, 2009
    r140 (Fix bug in listing command categories. Thanks to Yaroslav Ha...) committed by rocky.bernstein   -   Fix bug in listing command categories. Thanks to Yaroslav Halchenko for reporting the problem
    Fix bug in listing command categories. Thanks to Yaroslav Halchenko for reporting the problem
  • Sep 26, 2009
    r139 (Defensive programming) committed by rocky.bernstein   -   Defensive programming
    Defensive programming
  • Sep 26, 2009
    r138 (Improve selection of parameter name and use it more.) committed by rocky.bernstein   -   Improve selection of parameter name and use it more.
    Improve selection of parameter name and use it more.
  • Sep 26, 2009
    r137 (Some small typos) committed by rocky.bernstein   -   Some small typos
    Some small typos
 
Hosted by Google Code