1. 20 May, 1998 7 commits
  2. 19 May, 1998 21 commits
  3. 18 May, 1998 9 commits
  4. 16 May, 1998 2 commits
    • Guido van Rossum's avatar
      Fix another oldie (item (b) only): · c85be6a0
      Guido van Rossum authored
      Date:    Fri, 20 Dec 1996 14:47:50 +0100
      From:    Lele Gaifax <lele@nautilus.eclipse.it>
      To:      Python List <python-list@cwi.nl>
      Subject: Typos in ref manual
      
      Hi all,
      browsing the reference manual I noticed what seem two small errors:
        a) in the list of keywords (section 2.3.1) 'exec' is missing
        b) in the Operator Precedence table (5.12) the comparison operators
           include '=', but probably '==' was intended.
      Hope this help,
      lele.
      c85be6a0
    • Guido van Rossum's avatar
      Install config.h. · b9d9d72a
      Guido van Rossum authored
      Adapt to new build conventions (get rid of Release directory).
      b9d9d72a
  5. 15 May, 1998 1 commit
    • Guido van Rossum's avatar
      Another veeeeeery old patch... · fccfe897
      Guido van Rossum authored
      Date:    Thu, 14 Sep 1995 12:18:20 -0400
      From:    Alan Morse <alan@dvcorp.com>
      To:      python-list@cwi.nl
      Subject: getargs bug in 1.2 and 1.3 BETA
      
      We have found a bug in the part of the getargs code that we added
      and submitted, and which was incorporated into 1.1.
      
      The parsing of "O?" format specifiers is not handled correctly;
      there is no "else" for the "if" and therefore it can never fail.
      What's worse, the advancing of the varargs pointer is not
      handled properly, so from then on it is out of sync, wreaking
      all sorts of havoc. (If it had failed properly, then the out-of-sync
      varargs would not have been an issue.)
      
      Below is the context diff for the change.
      
      Note that I have made a few stylistic changes beyond adding the
      else case, namely:
      
      1) Making the "O" case follow the convention established by the other
      format specifiers of getting all their vararg arguments before
      performing the test, rather than getting some before and some after
      the test passes.
      
      2) Making the logic of the tests parallel, so the "if" part indicates
      that the format is accepted and the "else" part indicates that the
      format has failed. They were inconsistent with each other and with the
      the other format specifiers.
      
      -Alan Morse (amorse@dvcorp.com)
      fccfe897