headers
SourceForge.net | 1 Jan 2005 06:48
Picon
Favicon

[ python-Bugs-1091740 ] garbage collector still documented as optional

Bugs item #1091740, was opened at 2004-12-27 10:38
Message generated for change (Settings changed) made by rhettinger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1091740&group_id=5470

Category: Documentation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Gregory H. Ball (greg_ball)
>Assigned to: Raymond Hettinger (rhettinger)
Summary: garbage collector still documented as optional

Initial Comment:
Section 3.2 of the library reference, first paragraph, says
"The gc module is only available if the interpreter was
built with the optional cyclic garbage detector"

However according to Misc/NEWS, "Compiling out the
cyclic garbage collector is no longer an option" as of
Python 2.3 alpha 1.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1091740&group_id=5470
_______________________________________________
Python-bugs-list mailing list 
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Jan 2005 07:18
Picon
Favicon

[ python-Bugs-1092502 ] Memory leak in socket.py on Mac OS X 10.3

Bugs item #1092502, was opened at 2004-12-28 21:09
Message generated for change (Comment added) made by etrepum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092502&group_id=5470

Category: Python Library
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: bacchusrx (bacchusrx)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in socket.py on Mac OS X 10.3

Initial Comment:
Some part of socket.py leaks memory on Mac OS X 10.3 (both with 
the python 2.3 that ships with the OS and with python 2.4).

I encountered the problem in John Goerzen's offlineimap. 
Transfers of messages over a certain size would cause the program 
to bail with malloc errors, eg

*** malloc: vm_allocate(size=5459968) failed (error code=3)
*** malloc[13730]: error: Can't allocate region

Inspecting the process as it runs shows that python's total memory
size grows wildly during such transfers.

The bug manifests in _fileobject.read() in socket.py. You can 
replicate the problem easily using the attached example with "nc -l
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Jan 2005 07:27
Picon
Favicon

[ python-Bugs-1092502 ] Memory leak in socket.py on Mac OS X 10.3

Bugs item #1092502, was opened at 2004-12-28 21:09
Message generated for change (Comment added) made by etrepum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092502&group_id=5470

Category: Python Library
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: bacchusrx (bacchusrx)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in socket.py on Mac OS X 10.3

Initial Comment:
Some part of socket.py leaks memory on Mac OS X 10.3 (both with 
the python 2.3 that ships with the OS and with python 2.4).

I encountered the problem in John Goerzen's offlineimap. 
Transfers of messages over a certain size would cause the program 
to bail with malloc errors, eg

*** malloc: vm_allocate(size=5459968) failed (error code=3)
*** malloc[13730]: error: Can't allocate region

Inspecting the process as it runs shows that python's total memory
size grows wildly during such transfers.

The bug manifests in _fileobject.read() in socket.py. You can 
replicate the problem easily using the attached example with "nc -l
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Jan 2005 10:13
Picon
Favicon

[ python-Bugs-1092701 ] os.remove fails on win32 with read-only file

Bugs item #1092701, was opened at 2004-12-29 14:30
Message generated for change (Comment added) made by aminusfu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092701&group_id=5470

Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Joshua Weage (jpweage)
Assigned to: Nobody/Anonymous (nobody)
Summary: os.remove fails on win32 with read-only file

Initial Comment:
On Windows XP SP2 and Python 2.3.3 or 2.4 a call to
os.remove returns Errno 13 permission denied on a
read-only file.  On linux, python will delete a
read-only file.

----------------------------------------------------------------------

Comment By: Robert Brewer (aminusfu)
Date: 2005-01-01 09:13

Message:
Logged In: YES 
user_id=967320

Yup. I can reproduce that on Win2k.
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Jan 2005 18:17
Picon
Favicon

[ python-Bugs-1092225 ] IDLE hangs due to subprocess

Bugs item #1092225, was opened at 2004-12-28 10:31
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092225&group_id=5470

Category: IDLE
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: ZACK (kitanek)
>Assigned to: Kurt B. Kaiser (kbk)
Summary: IDLE hangs due to subprocess

Initial Comment:
IDLE GUI hangs after some time when launched in the
default mode (i.e. with the subprocess).
I have noticed that the subprocess generates fast
continuous stream of system calls even if the GUI is
not used and not visible (moved to another desktop).
Example output from strace (strace -f idle):

...
[pid  5359] <... select resumed> )      = 0 (Timeout)
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] select(4, [3], [], [], {0, 50000}
<unfinished ...>
[pid  5355] <... futex resumed> )       = -1 ETIMEDOUT
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Jan 2005 21:28
Picon
Favicon

[ python-Feature Requests-846560 ] Slicing infinity

Feature Requests item #846560, was opened at 2003-11-21 13:02
Message generated for change (Comment added) made by apb_4
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=846560&group_id=5470

Category: Python Interpreter Core
Group: None
Status: Closed
Resolution: Rejected
Priority: 5
Submitted By: Alexander Rødseth (alexanro)
Assigned to: Michael Hudson (mwh)
Summary: Slicing infinity

Initial Comment:
It would be great to be able to use extended slices
instead of range.

Here's an example:

&gt;&gt;&gt; for i in [0:10:2]:
...    print i
...
0
2
4
6
8

A more explicit (but longer) way to write this, could be:
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 2 Jan 2005 00:01
Picon
Favicon

[ python-Bugs-1092502 ] Memory leak in socket.py on Mac OS X 10.3

Bugs item #1092502, was opened at 2004-12-28 21:09
Message generated for change (Comment added) made by bacchusrx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092502&group_id=5470

Category: Python Library
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: bacchusrx (bacchusrx)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in socket.py on Mac OS X 10.3

Initial Comment:
Some part of socket.py leaks memory on Mac OS X 10.3 (both with 
the python 2.3 that ships with the OS and with python 2.4).

I encountered the problem in John Goerzen's offlineimap. 
Transfers of messages over a certain size would cause the program 
to bail with malloc errors, eg

*** malloc: vm_allocate(size=5459968) failed (error code=3)
*** malloc[13730]: error: Can't allocate region

Inspecting the process as it runs shows that python's total memory
size grows wildly during such transfers.

The bug manifests in _fileobject.read() in socket.py. You can 
replicate the problem easily using the attached example with "nc -l
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 2 Jan 2005 01:29
Picon
Favicon

[ python-Feature Requests-985094 ] getattr(object, name) accepts only strings

Feature Requests item #985094, was opened at 2004-07-05 01:21
Message generated for change (Comment added) made by complex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=985094&group_id=5470

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Viktor Ferenczi (complex)
Assigned to: Nobody/Anonymous (nobody)
Summary: getattr(object,name) accepts only strings

Initial Comment:
getattr(object,name) function accepts only strings. This behavior prohibits some interesting usage of
callables as names in database column and field references.

For example:

Someone references a database field:
value=record.field_name

Programmatically, when name is the name of the field:
value=getattr(record,field_name)

Calculated fields could be implemented by passing a callable as a field name:

def fn(record): return '%s (%s)'%(record.name,record.number)
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 2 Jan 2005 01:33
Picon
Favicon

[ python-Bugs-711268 ] A large block of commands after an &quot; if&quot; cannot be

Bugs item #711268, was opened at 2003-03-28 04:47
Message generated for change (Comment added) made by jepler
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=711268&group_id=5470

Category: Parser/Compiler
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Bram Moolenaar (vimboss)
Assigned to: Nobody/Anonymous (nobody)
Summary: A large block of commands after an &quot;if&quot; cannot be 

Initial Comment:
A Generated Python script Contains the code:
    if 1:
          file = bugreport.vim
          ... long list of commands ....

Executing this code with:
      exec cmds in globals(), globals()

Results in the error:
      SystemError: com_backpatch: offset too large

Looking into the code for com_backpatch() it appears
that the code is more than what can be jumped over.

Possible solutions:
(Continue reading)

Permalink | Reply | 3 comments |
headers
SourceForge.net | 2 Jan 2005 03:22
Picon
Favicon

[ python-Bugs-1092502 ] Memory leak in socket.py on Mac OS X 10.3

Bugs item #1092502, was opened at 2004-12-28 21:09
Message generated for change (Comment added) made by etrepum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092502&group_id=5470

Category: Python Library
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: bacchusrx (bacchusrx)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in socket.py on Mac OS X 10.3

Initial Comment:
Some part of socket.py leaks memory on Mac OS X 10.3 (both with 
the python 2.3 that ships with the OS and with python 2.4).

I encountered the problem in John Goerzen's offlineimap. 
Transfers of messages over a certain size would cause the program 
to bail with malloc errors, eg

*** malloc: vm_allocate(size=5459968) failed (error code=3)
*** malloc[13730]: error: Can't allocate region

Inspecting the process as it runs shows that python's total memory
size grows wildly during such transfers.

The bug manifests in _fileobject.read() in socket.py. You can 
replicate the problem easily using the attached example with "nc -l
(Continue reading)

Permalink | Reply | 0 comments |

Gmane