[ python-Bugs-1238170 ] threading.Thread uses {} as default argument

2005-07-14 Thread SourceForge.net
Bugs item #1238170, was opened at 2005-07-14 15:37
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238170&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Simon Dahlbacka (sdahlbac)
Assigned to: Nobody/Anonymous (nobody)
Summary: threading.Thread uses {} as default argument

Initial Comment:
threading.Thread.__init__ uses {} as default argument
for kwargs,
shouldn't this be the usual
def __init__(...,kwargs=None,...)
if kwargs is None:
kwargs = {}

In normal cases, this is probably not a problem but it
makes it possible to f*ck things up.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238170&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1238210 ] manual.cls contains an invalid pdf-inquiry

2005-07-14 Thread SourceForge.net
Bugs item #1238210, was opened at 2005-07-14 13:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Schindler (m-schindler)
Assigned to: Nobody/Anonymous (nobody)
Summary: manual.cls contains an invalid pdf-inquiry

Initial Comment:
I tried to compile the documentation for Python 2.4.1
(download today)
but it fails with the message:

  pdfTeX error (ext1): \pdfinfo used while \pdfoutput
is not set.

This is caused by the \pdfinfo call in manual.cls on
line 72.
I am using teTeX 3.0 where the LaTeX format is based on
pdftex. Therefore, the inquiry for pdf, done in
manual.cls with

  [EMAIL PROTECTED]
  
always returns true, for both pdf and dvi output.
A better choice woud be using \ifpdf defined in python.sty

Thanks, anyway for the great program!

  Michael Schindler

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1238210 ] manual.cls contains an invalid pdf-inquiry

2005-07-14 Thread SourceForge.net
Bugs item #1238210, was opened at 2005-07-14 13:43
Message generated for change (Settings changed) made by m-schindler
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Schindler (m-schindler)
Assigned to: Nobody/Anonymous (nobody)
Summary: manual.cls contains an invalid pdf-inquiry

Initial Comment:
I tried to compile the documentation for Python 2.4.1
(download today)
but it fails with the message:

  pdfTeX error (ext1): \pdfinfo used while \pdfoutput
is not set.

This is caused by the \pdfinfo call in manual.cls on
line 72.
I am using teTeX 3.0 where the LaTeX format is based on
pdftex. Therefore, the inquiry for pdf, done in
manual.cls with

  [EMAIL PROTECTED]
  
always returns true, for both pdf and dvi output.
A better choice woud be using \ifpdf defined in python.sty

Thanks, anyway for the great program!

  Michael Schindler

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1071094 ] some latex reject the pdfinfo macro while generating html

2005-07-14 Thread SourceForge.net
Bugs item #1071094, was opened at 2004-11-22 17:15
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1071094&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.4
>Status: Closed
>Resolution: Duplicate
Priority: 5
Submitted By: Marc-Antoine Parent (maparent)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: some latex reject the pdfinfo  macro while generating html

Initial Comment:
I was building the documentation on OSX. I use the latest LaTeX 
2004 from Wierda's teTeX. There is a pdfinfo command in Doc/
texinputs/manual.cls and Doc/texinputs/howto.cls which chokes my 
version of latex.

edited log follows:

TEXINPUTS=/.../Python-2.4c1/Doc/commontex: python /.../Python
-2.4c1/Doc/tools/mkhowto --html --about html/stdabout.dat --
iconserver ../icons --favicon ../icons/pyfav.png --address "See 
About this document... for 
information on suggesting changes." --up-link ../index.html --up-
title "Python Documentation Index" --global-module-index "../
modindex.html" --dvips-safe --dir html/api api/api.tex
+++ TEXINPUTS=/.../Python-2.4c1/
Doc/api:/.../Python-2.4c1/Doc/
commontex:/.../Python-2.4c1/Doc/
paper-letter:/.../Python-2.4c1/Doc/
texinputs:
+++ latex api
*** Session transcript and error messages are in /.../Python
-2.4c1/Doc/html/api/api.how.
*** Exited with status 1.
The relevant lines from the transcript are:

+++ latex api
This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3)
output format initialized to DVI
entering extended mode
(/.../Python-2.4c1/Doc/api/api.tex
LaTeX2e <2003/12/01>
Babel  and hyphenation patterns for american, french, 
german, ngerman, nohyphenation, loaded.
(/.../Python-2.4c1/Doc/texinputs/manual.cls
Document Class: manual 1998/03/03 Document class (Python 
manual)
(/.../Python-2.4c1/Doc/texinputs/pypaper.sty
(/usr/local/teTeX/share/texmf.tetex/tex/latex/psnfss/times.sty)
Using Times instead of Computer Modern.
) (/usr/local/teTeX/share/texmf.tetex/tex/latex/fancybox/
fancybox.sty
Style option: `fancybox' v1.3 <2000/09/19> (tvz)
) (/usr/local/teTeX/share/texmf.tetex/tex/latex/base/report.cls
Document Class: report 2004/02/16 v1.4f Standard LaTeX 
document class
(/usr/local/teTeX/share/texmf.tetex/tex/latex/base/size10.clo))
(/.../Python-2.4c1/Doc/texinputs/fancyhdr.sty)
Using fancier footers than usual.
(/.../Python-2.4c1/Doc/texinputs/fncychap.sty)
Using fancy chapter headings.
(/.../Python-2.4c1/Doc/texinputs/python.sty
(/usr/local/teTeX/share/texmf.tetex/tex/latex/tools/longtable.sty)
(/usr/local/teTeX/share/texmf.tetex/tex/latex/tools/verbatim.sty)
(/usr/local/teTeX/share/texmf.tetex/tex/latex/base/alltt.sty)))
(/.../Python-2.4c1/Doc/commontex/boilerplate.tex
(/.../Python-2.4c1/Doc/commontex/patchlevel.tex))
Writing index file api.idx
No file api.aux.
(/usr/local/teTeX/share/texmf.tetex/tex/latex/psnfss/ot1ptm.fd)
pdfTeX error (ext1): \pdfinfo used while \pdfoutput is not set.
 { \def \{, } \pdfinfo 
  { /Author ([EMAIL PROTECTED] ) /Title ([EMAIL 
PROTECTED] ) } }
l.12 \maketitle
   
No pages of output.
Transcript written on api.log.
*** Session transcript and error messages are in /.../Python
-2.4c1/Doc/html/api/api.how.
*** Exited with status 1.
make: *** [html/api/api.html] Error 1


--

>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 18:56

Message:
Logged In: YES 
user_id=1188172

Duplicate of #1238210.

--

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-06-07 22:33

Message:
Logged In: YES 
user_id=1188172

FWIW, problem exists and patch works for me. Linux 2.6,
teTeX 3.0.

--

Comment By: Sébastien Maret (bmaret)
Date: 2005-06-06 23:29

Message:
Logged In: YES 
user_id=842097

The patch worked for me (MacOSX 10.4.1, teTeX 3.0).
Thanks.

--

Comment By: Michael Ströder (stroeder)
Date: 2005-05-30 11:23

Message:
Logged In: YES 
user_id=64920

This patch I got from a tex expert seems to fix it. It
should also be applied to howto.cls.

--- manual.cls.orig 2005-05-30 10:02:28.0 +0200
+++ manual.cls  2005-05-30 11:16:58.0 +0200
@@ -6,9 +6,17 @@
 \ProvidesClass{manual}
  [1998/03/03 Document class (Python manual)]
 
+\RequirePackage{ifpdf}
[EMAIL PROTECTED]
+  \ifpdf
+[EMAIL PROTECTED]
+  \else
+[EMAIL PROTECTED]
+  \fi
+}
+
 \RequirePackage{pypaper}
 \RequirePackage{fancybox}
-
 % Change the options here to get a different set of basic
options, but only
 % if

[ python-Bugs-1238210 ] manual.cls contains an invalid pdf-inquiry

2005-07-14 Thread SourceForge.net
Bugs item #1238210, was opened at 2005-07-14 15:43
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Schindler (m-schindler)
Assigned to: Nobody/Anonymous (nobody)
Summary: manual.cls contains an invalid pdf-inquiry

Initial Comment:
I tried to compile the documentation for Python 2.4.1
(download today)
but it fails with the message:

  pdfTeX error (ext1): \pdfinfo used while \pdfoutput
is not set.

This is caused by the \pdfinfo call in manual.cls on
line 72.
I am using teTeX 3.0 where the LaTeX format is based on
pdftex. Therefore, the inquiry for pdf, done in
manual.cls with

  [EMAIL PROTECTED]
  
always returns true, for both pdf and dvi output.
A better choice woud be using \ifpdf defined in python.sty

Thanks, anyway for the great program!

  Michael Schindler

--

>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 18:57

Message:
Logged In: YES 
user_id=1188172

Seems to be also in howto.cls. Closed bug #1071094 as
duplicate of this.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1238210 ] manual.cls contains an invalid pdf-inquiry

2005-07-14 Thread SourceForge.net
Bugs item #1238210, was opened at 2005-07-14 15:43
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Schindler (m-schindler)
Assigned to: Nobody/Anonymous (nobody)
Summary: manual.cls contains an invalid pdf-inquiry

Initial Comment:
I tried to compile the documentation for Python 2.4.1
(download today)
but it fails with the message:

  pdfTeX error (ext1): \pdfinfo used while \pdfoutput
is not set.

This is caused by the \pdfinfo call in manual.cls on
line 72.
I am using teTeX 3.0 where the LaTeX format is based on
pdftex. Therefore, the inquiry for pdf, done in
manual.cls with

  [EMAIL PROTECTED]
  
always returns true, for both pdf and dvi output.
A better choice woud be using \ifpdf defined in python.sty

Thanks, anyway for the great program!

  Michael Schindler

--

>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 19:00

Message:
Logged In: YES 
user_id=1188172

This is the fix from the old bug.

--- manual.cls.orig 2005-05-30 10:02:28.0 +0200
+++ manual.cls  2005-05-30 11:16:58.0 +0200
@@ -6,9 +6,17 @@
 \ProvidesClass{manual}
  [1998/03/03 Document class (Python manual)]
 
+\RequirePackage{ifpdf}
[EMAIL PROTECTED]
+  \ifpdf
+[EMAIL PROTECTED]
+  \else
+[EMAIL PROTECTED]
+  \fi
+}
+
 \RequirePackage{pypaper}
 \RequirePackage{fancybox}
-
 % Change the options here to get a different set of basic
options, but only
 % if you have to.  Paper and font size should be adjusted
in pypaper.sty.
 %
@@ -64,7 +72,7 @@
 \let\footnotesize\small
 \let\footnoterule\relax
 [EMAIL PROTECTED]
-[EMAIL PROTECTED]
+[EMAIL PROTECTED]
   % This \def is required to deal with multi-line
authors; it
   % changes \ to ', ' (comma-space), making it pass
muster for
   % generating document info in the PDF file.

--

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 18:57

Message:
Logged In: YES 
user_id=1188172

Seems to be also in howto.cls. Closed bug #1071094 as
duplicate of this.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1238210 ] manual.cls contains an invalid pdf-inquiry

2005-07-14 Thread SourceForge.net
Bugs item #1238210, was opened at 2005-07-14 08:43
Message generated for change (Settings changed) made by rhettinger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Schindler (m-schindler)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: manual.cls contains an invalid pdf-inquiry

Initial Comment:
I tried to compile the documentation for Python 2.4.1
(download today)
but it fails with the message:

  pdfTeX error (ext1): \pdfinfo used while \pdfoutput
is not set.

This is caused by the \pdfinfo call in manual.cls on
line 72.
I am using teTeX 3.0 where the LaTeX format is based on
pdftex. Therefore, the inquiry for pdf, done in
manual.cls with

  [EMAIL PROTECTED]
  
always returns true, for both pdf and dvi output.
A better choice woud be using \ifpdf defined in python.sty

Thanks, anyway for the great program!

  Michael Schindler

--

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 12:00

Message:
Logged In: YES 
user_id=1188172

This is the fix from the old bug.

--- manual.cls.orig 2005-05-30 10:02:28.0 +0200
+++ manual.cls  2005-05-30 11:16:58.0 +0200
@@ -6,9 +6,17 @@
 \ProvidesClass{manual}
  [1998/03/03 Document class (Python manual)]
 
+\RequirePackage{ifpdf}
[EMAIL PROTECTED]
+  \ifpdf
+[EMAIL PROTECTED]
+  \else
+[EMAIL PROTECTED]
+  \fi
+}
+
 \RequirePackage{pypaper}
 \RequirePackage{fancybox}
-
 % Change the options here to get a different set of basic
options, but only
 % if you have to.  Paper and font size should be adjusted
in pypaper.sty.
 %
@@ -64,7 +72,7 @@
 \let\footnotesize\small
 \let\footnoterule\relax
 [EMAIL PROTECTED]
-[EMAIL PROTECTED]
+[EMAIL PROTECTED]
   % This \def is required to deal with multi-line
authors; it
   % changes \ to ', ' (comma-space), making it pass
muster for
   % generating document info in the PDF file.

--

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-14 11:57

Message:
Logged In: YES 
user_id=1188172

Seems to be also in howto.cls. Closed bug #1071094 as
duplicate of this.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238210&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1234850 ] Admin privs required for Windows?

2005-07-14 Thread SourceForge.net
Bugs item #1234850, was opened at 2005-07-08 11:52
Message generated for change (Comment added) made by bsherwood
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1234850&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Distutils
Group: Python 2.3
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Tim Peters (tim_one)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin privs required for Windows?

Initial Comment:
Over in ZopeLand, there's a complaint that the ZODB 
Windows installer requires admin privileges (or 
something like that):

http://www.zope.org/Collectors/Zope/1838

The installer was produced using Python 2.3.5, via

python setup.py bdist_wininst

from the root of a ZODB checkout.  Anyone have a 
guess as to what privs it needs that it might not 
have?  The user says they do have permission to write 
into their Python installation directory, so that's 
not it.  The message they get is "You do not seem to 
have sufficient access rights on this machine to 
install this software". 

Status under Python 2.4.1 is unknown.

--

Comment By: Bruce Sherwood (bsherwood)
Date: 2005-07-14 22:25

Message:
Logged In: YES 
user_id=34881

Debbie Carraway in IT at NCSU gives this important analysis
(she discovered this in the context of using the installer
for VPython, which looks for Python 2.4 in
HKLM\Software\Python\PythonCore\2.4\InstallPath; this used
to work with Python 2.3):

The problem is with the Python 2.4.1 installer. Python will
put the InstallPath registry setting (which indicates where
Python is installed)  under HKEY_CURRENT_USER instead of
HKEY_LOCAL_MACHINE under some circumstances:
 (1) if you are not a member of the Administrators group
 (2) if you choose "Install for Just Me" rather than
"Install for All Users",
 (3) if you automate the Python install using "msiexec.exe
/i python-2.4.1.msi /q". The /q (quiet) switch causes
different behavior than the defaults with a manual install
("msiexec.exe /i python-2.4.1.msi").

This is a mistake in the Python installer. The path to an
installed application always belongs under HKLM, because the
path to installed software is a machine-specific setting. If
the path is in HKCU, the InstallPath setting can follow a
user to a machine where Python is not installed. 

--

Comment By: Martin v. Löwis (loewis)
Date: 2005-07-11 12:55

Message:
Logged In: YES 
user_id=21627

The message comes from
PC\bdist_wininst\install.c:OpenLogFile, when attempting to
write to Software\Microsoft\CurrentVersion\Uninstall.
Whether this goes to HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE
apparently depends on whether Python was installed per-user
or per-machine.

In the 2.4.1 version, in CheckRootKey, there is a
HasLocalMachinePrivs function. Mark Hammond added this in
install.c 1.6 in response to #555812 and #555810, so I'm
declaring this bug fixed.

--

Comment By: Tim Peters (tim_one)
Date: 2005-07-08 14:59

Message:
Logged In: YES 
user_id=31435

Bug 1232947 is about installing Python itself.  This one is 
about installing a 3rd-party package that happens to use 
Python (a pre-existing Python), using a Windows installer 
created by Python's distutils package.  It's unlikely the bugs 
have anything in common.

--

Comment By: Patrick Vrijlandt (pvrijlandt)
Date: 2005-07-08 14:48

Message:
Logged In: YES 
user_id=1307917

Did you see bug # 1232947? It provides documentation of 
another failing non-admin install. (2.4.1).


--

Comment By: Tim Peters (tim_one)
Date: 2005-07-08 13:11

Message:
Logged In: YES 
user_id=31435

You should be able to try 2.4.  The Python installer includes 
msvcr71.dll, and should install it into the Python directory 
(instead of into a system directory) is you do a "install just 
for me" (as opposed to "all users") install.

--

Comment By: Alex (hairypalm)
Date: 2005-07-08 12:36

Message:
Logged In: YES 
user_id=1309592

I am the original "complainant".  I cannot try python 2.4 
install package because it requires MSVCR71.dll.  I 
am "locked down" at work and cannot write files except to 
my own user area.  I am also prevented from writing to some 
areas of the registry.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1234850&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://ma

[ python-Bugs-1238681 ] freed pointer is used in longobject.c:long_pow()

2005-07-14 Thread SourceForge.net
Bugs item #1238681, was opened at 2005-07-15 15:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238681&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Luke (luked)
Assigned to: Nobody/Anonymous (nobody)
Summary: freed pointer is used in longobject.c:long_pow()

Initial Comment:
See in the following code snippet (from the end of the
long_pow function in longobject.c) that "b" is used
after it has been freed:

 Done:
Py_XDECREF(a);
Py_XDECREF(b);
Py_XDECREF(c);
Py_XDECREF(temp);
if (b->ob_size > FIVEARY_CUTOFF) {
for (i = 0; i < 32; ++i)
Py_XDECREF(table[i]);
}
return (PyObject *)z;
}

The error exists in 2.4.1 and on CVS trunk.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238681&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1238681 ] freed pointer is used in longobject.c:long_pow()

2005-07-14 Thread SourceForge.net
Bugs item #1238681, was opened at 2005-07-15 00:06
Message generated for change (Comment added) made by rhettinger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238681&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
>Group: Python 2.4
Status: Open
Resolution: None
>Priority: 7
Submitted By: Luke (luked)
>Assigned to: Tim Peters (tim_one)
Summary: freed pointer is used in longobject.c:long_pow()

Initial Comment:
See in the following code snippet (from the end of the
long_pow function in longobject.c) that "b" is used
after it has been freed:

 Done:
Py_XDECREF(a);
Py_XDECREF(b);
Py_XDECREF(c);
Py_XDECREF(temp);
if (b->ob_size > FIVEARY_CUTOFF) {
for (i = 0; i < 32; ++i)
Py_XDECREF(table[i]);
}
return (PyObject *)z;
}

The error exists in 2.4.1 and on CVS trunk.


--

>Comment By: Raymond Hettinger (rhettinger)
Date: 2005-07-15 00:26

Message:
Logged In: YES 
user_id=80475

Tim, I believe this one belongs to you (checkin 1.163 on
8/30/2004).

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1238681&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com