[ python-Bugs-1201438 ] Wrong word on "raise" page

2005-05-13 Thread SourceForge.net
Bugs item #1201438, was opened at 2005-05-13 11:23
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=1201438&group_id=5470

Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Erik Rose (grincheroo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong word on "raise" page

Initial Comment:
At http://python.org/doc/2.4.1/ref/raise.html, the first occurrence of 
"last expression" should be "last exception". This is corroborated by 
the next clause, which reads, correctly, "If no exception is active in 
the current scope...".

Thanks for fine docs!
Erik

--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

2005-05-13 Thread SourceForge.net
Bugs item #1201456, was opened at 2005-05-13 19: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=1201456&group_id=5470

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

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

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

>Comment By: Michael Hudson (mwh)
Date: 2005-05-13 16:46

Message:
Logged In: YES 
user_id=6656

I see no code.  SF can be a pain with this...

--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

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

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

>Comment By: Vladimir Yu. Stepanov (vys)
Date: 2005-05-13 19:46

Message:
Logged In: YES 
user_id=384980

d = {} 
 
class test: 
def __hash__(self): 
d[self] = None 
 
d[test()] = None 

--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 19:46

Message:
Logged In: YES 
user_id=6656

I see no code.  SF can be a pain with this...

--

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



[ python-Bugs-1201461 ] suspected cPickle memory leak

2005-05-13 Thread SourceForge.net
Bugs item #1201461, was opened at 2005-05-13 15:49
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=1201461&group_id=5470

Category: Python Library
Group: Python 2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Alan (franz2)
Assigned to: Nobody/Anonymous (nobody)
Summary: suspected cPickle memory leak 

Initial Comment:
I believe there is a memory leak in cPickle.  I
have a parallel code which uses array() and indices()
from Numeric to massage data buffers before being sent
and received by Pypar.  Pypar subsequently uses cPickle
to pickle the data.  After many hours of execution, my
code crashes with one of the following error messages
(depending upon the run):


a = zeros(shape, typecode, savespace)
MemoryError:  can't allocate memory for array


or:


s = dumps(x, 1)
MemoryError:  out of memory


I have since modified my code to use a different data
format so cPickle is no longer used from PyPar and now
the code runs fine.


--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

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

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

>Comment By: Michael Hudson (mwh)
Date: 2005-05-13 16:55

Message:
Logged In: YES 
user_id=6656

I get an infinite recursion runtime error.  What platform
are you on?

--

Comment By: Vladimir Yu. Stepanov (vys)
Date: 2005-05-13 16:46

Message:
Logged In: YES 
user_id=384980

d = {} 
 
class test: 
def __hash__(self): 
d[self] = None 
 
d[test()] = None 

--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 16:46

Message:
Logged In: YES 
user_id=6656

I see no code.  SF can be a pain with this...

--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

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

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

>Comment By: Raymond Hettinger (rhettinger)
Date: 2005-05-13 10:55

Message:
Logged In: YES 
user_id=80475

I get the expected behavior:

  RuntimeError: maximum recursion depth exceeded


--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 10:55

Message:
Logged In: YES 
user_id=6656

I get an infinite recursion runtime error.  What platform
are you on?

--

Comment By: Vladimir Yu. Stepanov (vys)
Date: 2005-05-13 10:46

Message:
Logged In: YES 
user_id=384980

d = {} 
 
class test: 
def __hash__(self): 
d[self] = None 
 
d[test()] = None 

--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 10:46

Message:
Logged In: YES 
user_id=6656

I see no code.  SF can be a pain with this...

--

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



[ python-Bugs-1201438 ] Wrong word on "raise" page

2005-05-13 Thread SourceForge.net
Bugs item #1201438, was opened at 2005-05-13 10:23
Message generated for change (Comment added) made by rhettinger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1201438&group_id=5470

Category: Documentation
Group: None
>Status: Closed
>Resolution: Duplicate
Priority: 5
Submitted By: Erik Rose (grincheroo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong word on "raise" page

Initial Comment:
At http://python.org/doc/2.4.1/ref/raise.html, the first occurrence of 
"last expression" should be "last exception". This is corroborated by 
the next clause, which reads, correctly, "If no exception is active in 
the current scope...".

Thanks for fine docs!
Erik

--

>Comment By: Raymond Hettinger (rhettinger)
Date: 2005-05-13 10:58

Message:
Logged In: YES 
user_id=80475

This duplicates SF bug #1190451 which was fixed on 4/28/2005.

--

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



[ python-Bugs-1201456 ] Problem with recursion in dict (crash with core dump)

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

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Yu. Stepanov (vys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with recursion in dict (crash with core dump)

Initial Comment:
Please see example code. 

--

>Comment By: Vladimir Yu. Stepanov (vys)
Date: 2005-05-13 20:06

Message:
Logged In: YES 
user_id=384980

This is output from `uname -a`: 
FreeBSD fox.renet.ru 5.3-RELEASE FreeBSD 5.3-RELEASE 
#1: Fri Apr 15 10:38:49 MSD 2005 
[EMAIL PROTECTED]:/M/safedir/src/sys/i386/compile/FOX  i386 
 
I get some others with this code: 
 
Python 2.4.1 (#2, Apr 26 2005, 14:16:31) 
[GCC 3.4.2 [FreeBSD] 20040728] on freebsd5 
Type "help", "copyright", "credits" or "license" for more 
information. 
>>> d = {} 
>>> 
>>> class test: 
... def __hash__(self): 
... d[self] = None 
... 
>>> d[test()] = None 
Bus error (core dumped) 
 
 
fox:vys!~ > gdb python python.core 
GNU gdb 6.1.1 [FreeBSD] 
Copyright 2004 Free Software Foundation, Inc. 
GDB is free software, covered by the GNU General Public 
License, and you are 
welcome to change it and/or distribute copies of it under 
certain conditions. 
Type "show copying" to see the conditions. 
There is absolutely no warranty for GDB.  Type "show 
warranty" for details. 
This GDB was configured as "i386-marcel-freebsd"...(no 
debugging symbols found)... 
Core was generated by `python'. 
Program terminated with signal 10, Bus error. 
 
(gdb) where 
#0  0x2828b3b1 in ldexp () from /lib/libc.so.5 
#1  0x2828b618 in malloc () from /lib/libc.so.5 
#2  0x080bdca1 in _PyObject_GC_Malloc () 
#3  0x080bdd4a in _PyObject_GC_New () 
#4  0x0805f556 in PyMethod_New () 
#5  0x0805c1a6 in PyInstance_NewRaw () 
#6  0x0805c66a in PyInstance_New () 
#7  0x0805cca1 in _PyInstance_Lookup () 
#8  0x080703e6 in PyDict_SetItem () 
#9  0x0809bb0e in PyEval_EvalFrame () 
#10 0x0809fc20 in PyEval_EvalCodeEx () 
#11 0x080d4d66 in PyFunction_SetClosure () 
#12 0x0805a38c in PyObject_Call () 
#13 0x0805fbe2 in PyMethod_New () 
#14 0x0805a38c in PyObject_Call () 
#15 0x08099f1b in PyEval_CallObjectWithKeywords () 
#16 0x0805ccb9 in _PyInstance_Lookup () 
#17 0x080703e6 in PyDict_SetItem () 
#18 0x0809bb0e in PyEval_EvalFrame () 
#19 0x0809fc20 in PyEval_EvalCodeEx () 
#20 0x080d4d66 in PyFunction_SetClosure () 
#21 0x0805a38c in PyObject_Call () 
#22 0x0805fbe2 in PyMethod_New () 
 

--

Comment By: Raymond Hettinger (rhettinger)
Date: 2005-05-13 19:55

Message:
Logged In: YES 
user_id=80475

I get the expected behavior:

  RuntimeError: maximum recursion depth exceeded


--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 19:55

Message:
Logged In: YES 
user_id=6656

I get an infinite recursion runtime error.  What platform
are you on?

--

Comment By: Vladimir Yu. Stepanov (vys)
Date: 2005-05-13 19:46

Message:
Logged In: YES 
user_id=384980

d = {} 
 
class test: 
def __hash__(self): 
d[self] = None 
 
d[test()] = None 

--

Comment By: Michael Hudson (mwh)
Date: 2005-05-13 19:46

Message:
Logged In: YES 
user_id=6656

I see no code.  SF can be a pain with this...

--

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



[ python-Bugs-1198275 ] time module ignores timezone changes

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

Category: Extension Modules
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: David Lambert (jdalambert)
Assigned to: Brett Cannon (bcannon)
Summary: time module ignores timezone changes

Initial Comment:
Running on Fedora Core 3 Linux

Consider the simple program

import time

while 1:
  print time.localtime()
  time.sleep(1)


The tuple printed by this program does not reflect any
change in the system timezone until the interpreter is
exited and restarted. Using reload(time) does not fix
the problem. Are there any workarounds?

--

>Comment By: David Lambert (jdalambert)
Date: 2005-05-13 14:07

Message:
Logged In: YES 
user_id=845425

Yes that worked fine thanks. I guess I just had not been
Reading The (updated) Fine Manual :-(

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-11 15:35

Message:
Logged In: YES 
user_id=357491

OK, fixed the version and reopened this.

No, you don't need to poll, just call time.tzset() before
you call time.localtime() or anything else that relies on
the timezone.  It isn't that expensive of a call.  Post here
if that fixes it or not.

And in terms of inelegance, the only other solution is to
implicitly call time.tzset() internally for all time
functions.  This is an issue imposed by the ISO C libraries.

--

Comment By: David Lambert (jdalambert)
Date: 2005-05-10 21:33

Message:
Logged In: YES 
user_id=845425

Ouch! I don't know how I got 2.2.3 on the bug report? My
version of Python is 2.3.4. Sorry for the confusion.:-( Let
me explain further. The problem is that I have a Python
script that is run as a daemon and uses localtime(). If
another program (outside of my control) changes the
timezone, the my daemon gets the local time according to the
original timezone. Do I have to periodically poll to see if
the timezone has changed? That seems somewhat inelegant.

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-10 18:10

Message:
Logged In: YES 
user_id=357491

Wait, I just noticed after I sent my follow-up that this bug
report is against Python 2.2.3 .  You won't find
time.tzset() that far back.  The issue is that you need to
use time.tzset() to reset the timezone for the C library
functions to use any change you have made since they cache
information internally.

I am closing this as "won't fix" since it has been resolved
in later versions and 2.2 is too old to bother backporting for.

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-10 18:07

Message:
Logged In: YES 
user_id=357491

David, how did you change the timezone?  And did you call
time.tzset()?  If you didn't call time.tzset(), that's the
problem.  If you did, then there is a bug.

--

Comment By: Raymond Hettinger (rhettinger)
Date: 2005-05-09 22:09

Message:
Logged In: YES 
user_id=80475

Brett, are you still in the time business?

--

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



[ python-Bugs-1198275 ] time module ignores timezone changes

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

Category: Extension Modules
Group: Python 2.3
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: David Lambert (jdalambert)
Assigned to: Brett Cannon (bcannon)
Summary: time module ignores timezone changes

Initial Comment:
Running on Fedora Core 3 Linux

Consider the simple program

import time

while 1:
  print time.localtime()
  time.sleep(1)


The tuple printed by this program does not reflect any
change in the system timezone until the interpreter is
exited and restarted. Using reload(time) does not fix
the problem. Are there any workarounds?

--

>Comment By: Brett Cannon (bcannon)
Date: 2005-05-13 14:04

Message:
Logged In: YES 
user_id=357491

Cool, glad it worked out.

Closed as invalid.

--

Comment By: David Lambert (jdalambert)
Date: 2005-05-13 12:07

Message:
Logged In: YES 
user_id=845425

Yes that worked fine thanks. I guess I just had not been
Reading The (updated) Fine Manual :-(

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-11 13:35

Message:
Logged In: YES 
user_id=357491

OK, fixed the version and reopened this.

No, you don't need to poll, just call time.tzset() before
you call time.localtime() or anything else that relies on
the timezone.  It isn't that expensive of a call.  Post here
if that fixes it or not.

And in terms of inelegance, the only other solution is to
implicitly call time.tzset() internally for all time
functions.  This is an issue imposed by the ISO C libraries.

--

Comment By: David Lambert (jdalambert)
Date: 2005-05-10 19:33

Message:
Logged In: YES 
user_id=845425

Ouch! I don't know how I got 2.2.3 on the bug report? My
version of Python is 2.3.4. Sorry for the confusion.:-( Let
me explain further. The problem is that I have a Python
script that is run as a daemon and uses localtime(). If
another program (outside of my control) changes the
timezone, the my daemon gets the local time according to the
original timezone. Do I have to periodically poll to see if
the timezone has changed? That seems somewhat inelegant.

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-10 16:10

Message:
Logged In: YES 
user_id=357491

Wait, I just noticed after I sent my follow-up that this bug
report is against Python 2.2.3 .  You won't find
time.tzset() that far back.  The issue is that you need to
use time.tzset() to reset the timezone for the C library
functions to use any change you have made since they cache
information internally.

I am closing this as "won't fix" since it has been resolved
in later versions and 2.2 is too old to bother backporting for.

--

Comment By: Brett Cannon (bcannon)
Date: 2005-05-10 16:07

Message:
Logged In: YES 
user_id=357491

David, how did you change the timezone?  And did you call
time.tzset()?  If you didn't call time.tzset(), that's the
problem.  If you did, then there is a bug.

--

Comment By: Raymond Hettinger (rhettinger)
Date: 2005-05-09 20:09

Message:
Logged In: YES 
user_id=80475

Brett, are you still in the time business?

--

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



[ python-Bugs-1201807 ] Glossary listing bug

2005-05-13 Thread SourceForge.net
Bugs item #1201807, was opened at 2005-05-14 15:11
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=1201807&group_id=5470

Category: Documentation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: George Yoshida (quiver)
Assigned to: Nobody/Anonymous (nobody)
Summary: Glossary listing bug

Initial Comment:
On the glossary page[*], "duck-typing" is not recognized 
as an entry for glossary. Currently, the rendered html is:

  
  duck-typing Pythonic programming style ...

And this should look like:

  duck-typing
  Pythonic programming style ...

Replacing '{' mark with '[' mark should fix this.

   \index{duck-typing}
  -\item{duck-typing}
  +\item[duck-typing]

[*] http://docs.python.org/tut/node18.html


--

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