1. 09 Şub, 2001 2 kayıt (commit)
  2. 07 Şub, 2001 1 kayıt (commit)
  3. 20 Ock, 2001 1 kayıt (commit)
  4. 15 Ock, 2001 1 kayıt (commit)
  5. 14 Ock, 2001 1 kayıt (commit)
  6. 12 Ara, 2000 1 kayıt (commit)
  7. 16 Tem, 2000 1 kayıt (commit)
    • Thomas Wouters's avatar
      Spelling fixes supplied by Rob W. W. Hooft. All these are fixes in either · 7e474022
      Thomas Wouters yazdı
      comments, docstrings or error messages. I fixed two minor things in
      test_winreg.py ("didn't" -> "Didn't" and "Didnt" -> "Didn't").
      
      There is a minor style issue involved: Guido seems to have preferred English
      grammar (behaviour, honour) in a couple places. This patch changes that to
      American, which is the more prominent style in the source. I prefer English
      myself, so if English is preferred, I'd be happy to supply a patch myself ;)
      7e474022
  8. 06 Mar, 2000 1 kayıt (commit)
    • Guido van Rossum's avatar
      Sjoerd Mullender: · e85c93f5
      Guido van Rossum yazdı
      When you set a breakpoint on a function with a multi-line argument
      list, the breakpoint is actually set on the second line of the
      arguments instead of the first line of the body.  This patch fixes
      that.
      e85c93f5
  9. 04 Şub, 2000 2 kayıt (commit)
    • Guido van Rossum's avatar
      Actually, the previous batch's comment should have been different; · 4b8c6eaf
      Guido van Rossum yazdı
      *this* set of patches is Ka-Ping's final sweep:
      
      The attached patches update the standard library so that all modules
      have docstrings beginning with one-line summaries.
      
      A new docstring was added to formatter.  The docstring for os.py
      was updated to mention nt, os2, ce in addition to posix, dos, mac.
      4b8c6eaf
    • Guido van Rossum's avatar
      More trivial comment -> docstring transformations by Ka-Ping Yee, · 54f22ed3
      Guido van Rossum yazdı
      who writes:
      
      Here is batch 2, as a big collection of CVS context diffs.
      Along with moving comments into docstrings, i've added a
      couple of missing docstrings and attempted to make sure more
      module docstrings begin with a one-line summary.
      
      I did not add docstrings to the methods in profile.py for
      fear of upsetting any careful optimizations there, though
      i did move class documentation into class docstrings.
      
      The convention i'm using is to leave credits/version/copyright
      type of stuff in # comments, and move the rest of the descriptive
      stuff about module usage into module docstrings.  Hope this is
      okay.
      54f22ed3
  10. 03 Kas, 1999 1 kayıt (commit)
    • Guido van Rossum's avatar
      Sjoerd Mullender writes: · 19878f58
      Guido van Rossum yazdı
      I regularly find that pdb sets the breakpoint on the wrong line when I
      try to set a breakpoint on a function.  This fixes the problem
      somewhat.
      The real problem is that pdb tries to parse the Python source code to
      find the first executable line.  A better way might be to inspect the
      code object, or even have a variable in the code object
      co_firstexecutablelineno, but that's too much work.
      
      The patch fixes the problem when the first code line after the def
      statement contains the start *and* end of a triple-quoted string.  The
      code assumed that the end of a triple-quoted string is not on the same
      line as the start, and so it would skip to the end of the *next*
      triple-quoted string.
      19878f58
  11. 09 Eyl, 1999 1 kayıt (commit)
  12. 03 May, 1999 1 kayıt (commit)
  13. 28 Ock, 1999 1 kayıt (commit)
  14. 27 Ock, 1999 1 kayıt (commit)
  15. 25 Ock, 1999 1 kayıt (commit)
  16. 15 Eki, 1998 1 kayıt (commit)
  17. 17 Eyl, 1998 1 kayıt (commit)
  18. 11 Eyl, 1998 1 kayıt (commit)
    • Guido van Rossum's avatar
      Richard Wolff's changes: · 2424f855
      Guido van Rossum yazdı
      pdb.py  Uses the Breakpoint class so one can enable/disable breakpoints,
      	set temporary ones, set ignore counts, and conditions.  The last
      	can be set using the 'b' command
      		b 243 , i>4		( b 243,i>4 if you are space adverse)
      	or with the condition command so conditions can be changed
      	for a particular breakpoint.
      
      	Breakpoints are numbered from 1 on, and if a breakpoint is deleted,
      	the number is not reused.  All the breakpoint handling commands
      	refer to breakpoints by number.  To be consistent, the clear command
      	does so as well, which is the one change from the original pdb that
      	is not transparent.  Thus only the breakpoint command 'b' uses a
      	line number or file:line or method.  You can also give
      		b whrandom.random    and the method will be searched for along
      	sys.path.  This is implemented with an 'egrep' command and so
      	is not as portable as it might be.  [ see  lineinfo() and
      	lineinfoCmd ]
      
      	Breakpoints cannot be set at a line that is blank or a '#' comment
      	or starts a triply quoted comment.  This is because I would like
      	this behavior in my DDD interface and think it reasonable for
      	pdb as well.  It can be removed readily, however as it is all
      	incorporated in the routine checkline().  If one attempts to
      	set a breakpoint at a 'def' line, the breakpoint is automatically
      	moved to the first executable line after the 'def'.  This too is
      	in checkline().
      
      	do_EOF() returns zero so typing an end-of-file character as a command
      	does nothing.  'quit' does the quitting.
      
      	The routine defaultFile() is present so as to preserve the current
      	pdb behavior and yet allow me to override it in pydb.
      
      	There's some code in lineinfo() that is probably mainly useful only
      	for pydb and if you prefer, much up to the comment "Best first guess"
      	could be removed.
      
      	Keith Davidson provided the code for handling $HOME/.pdbrc and
      	./.pdbrc, and it has been incorporated.  He also provided the
      	alias handling routine.  I modified it a bit so it could live
      	nicely in precmd().  He and I have been in contact; he has the
      	new pdb (and pydb) with his code incorporated.  He also asked
      	about the possibility of allowing multiple commands on one
      	line, such as step;step  or s;s  or with an alias such as
      		alias ct tbreak %1 ; continue
      	and since it was so easy, that's in place as well.  It's a simple
      	'split the line at the first ";"' operation and puts the second
      	half in the command queue (self.cmdqueue).  This has the unfortunate
      	effect of destroying a line like   print "i: "+i+"; j: "+j
      	but either there's a simple way to deal with this, or my attitude
      	will remain that pdb is a debugger, not a compiler/parser/etc.
      	An alias like   alias 4s  s;;s;
      	will work because the adjacent and trailing ";" act like a <cr> which
      	repeats the last command.  Of course, either s;s;s;s or s;;;  would be
      	a bit more sensible.
      
      	The help commands have been updated.
      2424f855
  19. 22 Tem, 1998 1 kayıt (commit)
  20. 20 Tem, 1998 1 kayıt (commit)
    • Guido van Rossum's avatar
      Added support for specifying a filename for a breakpoint, roughly · b5699c72
      Guido van Rossum yazdı
      according to an idea by Harri Pasanen (but with different syntax).
      This affects the 'break' and 'clear' commands and their help
      functions.  Also added a helper method lookupmodule().
      
      Also:
      
      - Try to import readline (important when pdb is used from/as a script).
      - Get rid of reference to ancient __privileged__ magic variable.
      - Moved all import out of functions to the top.
      - When used as a script, check that the script file exists.
      b5699c72
  21. 25 Şub, 1998 1 kayıt (commit)
  22. 29 Eyl, 1997 1 kayıt (commit)
  23. 18 Tem, 1997 1 kayıt (commit)
  24. 11 Tem, 1997 1 kayıt (commit)
  25. 27 Kas, 1996 1 kayıt (commit)
  26. 10 Eyl, 1996 1 kayıt (commit)
  27. 30 Tem, 1996 1 kayıt (commit)
  28. 07 Agu, 1995 1 kayıt (commit)
  29. 27 Şub, 1995 1 kayıt (commit)
  30. 03 Şub, 1995 1 kayıt (commit)
  31. 10 Kas, 1994 1 kayıt (commit)
  32. 01 Agu, 1994 1 kayıt (commit)
  33. 17 Ara, 1993 1 kayıt (commit)
  34. 22 Eki, 1993 2 kayıt (commit)
  35. 29 Tem, 1993 1 kayıt (commit)
  36. 23 Haz, 1993 1 kayıt (commit)
  37. 29 Mar, 1993 1 kayıt (commit)