[issue2858] bsddb.db.DBEnv.lock_get test_lock.test03_set_timeout crashes
Gregory P. Smith [EMAIL PROTECTED] added the comment: I submitted a patch from Neal Norwitz after jcea reviewed it to trunk as r63403. I'll take care of backporting it to release25-maint. -- assignee: jcea - gregory.p.smith versions: -Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2858 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2858] bsddb.db.DBEnv.lock_get test_lock.test03_set_timeout crashes
Gregory P. Smith [EMAIL PROTECTED] added the comment: r63404 in release25-maint. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2858 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1275] bsddb closing a DB object before all DBCursors using it are closed crashes
Gregory P. Smith [EMAIL PROTECTED] added the comment: This is fixed in trunk now that jcea has done his merge. If anyone wants it fixed in release25-maint it'll need a volunteer to backport just the bugfix parts without the bsddb 4.6.x feature additions. -- assignee: gregory.p.smith - jcea priority: normal - low versions: -Python 2.4, Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1275 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1397] mysteriously failing test_bsddb3 threading test in other threads
Gregory P. Smith [EMAIL PROTECTED] added the comment: does this still apply to the current test suite Jesus? -- assignee: gregory.p.smith - jcea __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1397 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1010645] bsddb3 testsuite failure when running more than one time
Gregory P. Smith [EMAIL PROTECTED] added the comment: I believe this was finally cleaned up. There are still changes to be made to the current test suite (blindly using a directory under /tmp and not cleaning it up afterwards is bad) but the actual bug this refers to was fixed. -- resolution: - fixed status: open - closed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1010645 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue834461] simple bsddb interface potential for deadlock with threads
Gregory P. Smith [EMAIL PROTECTED] added the comment: This bug was created to track my FIXME in the code. Nobody else has commented on it. I doubt its an issue worth fixing. It is a valid FIXME but I'm marking it as low priority and leaving it unassigned just to track the issue incase someone actually does want to improve the legacy/simple bsddb interface. -- assignee: gregory.p.smith - priority: normal - low Tracker [EMAIL PROTECTED] http://bugs.python.org/issue834461 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1391] Adds the .compact() method to bsddb db.DB objects
Gregory P. Smith [EMAIL PROTECTED] added the comment: Jesus is the bsddb maintainer now. -- assignee: gregory.p.smith - jcea __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1391 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1215023] bsddb dbobj.DB.associate doesn't accept dbobj.DB param
Gregory P. Smith [EMAIL PROTECTED] added the comment: I think the workaround proposed in my email in this bug is sufficient. Blindly letting associate work on python wrapped overridden objects such that the underlying library doesn't call into the wrapper could confuse people. -- resolution: - wont fix status: open - closed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1215023 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2587] PyString_FromStringAndSize() to be considered unsafe
Gregory P. Smith [EMAIL PROTECTED] added the comment: the redundant asserts were removed. reclosing. further discussion on signedness issues in the code base should take place on the mailing list, future bugs or peps as appropriate. -- status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2587 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2632] performance problem in socket._fileobject.read
Gregory P. Smith [EMAIL PROTECTED] added the comment: I'm going to let the committed change bake in Python trunk for a beta release or two before backporting it to release25-maint. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2632 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2381] test_subprocess fails if your sys.executable is on a path with a space in it
Gregory P. Smith [EMAIL PROTECTED] added the comment: fixed in trunk r63405 -- priority: - normal resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2381 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2896] cmathmodule.c compilation error
Georg Brandl [EMAIL PROTECTED] added the comment: It would be a good thing to paste the exact error message from the compiler. -- nosy: +georg.brandl __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2896 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2896] cmathmodule.c compilation error
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: Hello. This issue seems to be fixed by r63385. (alexandre.vassalotti's merge) -- nosy: +ocean-city __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2896 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2896] cmathmodule.c compilation error
Georg Brandl [EMAIL PROTECTED] added the comment: Ah, it wasn't merged yet. So this can be closed. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2896 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
New submission from Robert Schuppenies [EMAIL PROTECTED]: I propose a patch which allows to query the memory footprint of an object. Calling 'footprint(o)', a python developer can retrieve the size of any python object. Only the size of the object itself will be returned, the size of any referenced objects will be ignored. The patch implements a generic function to compute the object size. This works in most, but a few cases. One of these exceptions is the dictionary with its particular table implementation. Such cases can be handled by implementing an optional method in C. This would also be the case for third-party implementations with unusual type definitions. One advantage with this approach is that the object size can be computed at the level an object is allocated, not requiring complex computations and considerations on higher levels. I am not completely happy with the name 'footprint', but think using 'sizeof' would be confused with plain 'size', and 'memory_usage' was somewhat too long to be typed conveniently. Current test pass on linux32 and linux64, but the test suite is not complete, yet. This patch is part of my Google Summer of Code project on Python memory profiling (http://code.google.com/soc/2008/psf/appinfo.html?csaid=13F0E9C8B6E064EF). Also, this is my first patch, so please let me know where missed something, did not follow coding conventions, or made wrong assumptions. -- components: Interpreter Core files: footprint.patch keywords: patch messages: 66989 nosy: okkoto severity: normal status: open title: Add memory footprint query type: feature request versions: Python 2.6 Added file: http://bugs.python.org/file10353/footprint.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Georg Brandl [EMAIL PROTECTED] added the comment: Can't you write this as a simple Python function using type.__basicsize__ and type.__itemsize__? In any case, if this is added somewhere it should not be a builtin. This operation is nowhere near the usefulness to be one. -- nosy: +georg.brandl __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Robert Schuppenies [EMAIL PROTECTED] added the comment: Can't you write this as a simple Python function using type.__basicsize__ and type.__itemsize__? Yes, it would be possible and has been done, e.g. http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/546530. The problem is though, that it requires handling of all special cases externally. Any changes need to be addressed separately and unknown type definitions cannot be addressed at all. Also I figured the programmer implementing a type would know best about its size. Another point is different architectures which result in different object sizes. In any case, if this is added somewhere it should not be a builtin. What place would you consider to be appropriate? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Georg Brandl [EMAIL PROTECTED] added the comment: Such implementation-specific things usually went into the sys module. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2899] Fixes find, rfind, etc in 'string' module
New submission from Haoyu Bai [EMAIL PROTECTED]: Functions like find() rfind() index() rindex() has been removed in Python 3.0. So there should be a 2to3 fix for it. Eg. fix if string.find(s, hello) = 0: to if str.find(s, hello) = 0: Thank you! -- assignee: collinwinter components: 2to3 (2.x to 3.0 conversion tool) messages: 66993 nosy: bhy, collinwinter severity: normal status: open title: Fixes find, rfind, etc in 'string' module type: feature request versions: Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2899 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Martin v. Löwis [EMAIL PROTECTED] added the comment: It's actually not possible, in general, to compute the memory consumption of an object using basicsize and itemsize. An example is the dictionary, where there is no way to find out how many slots are currently allocated. Even for the things such as lists where the formula basicsize+len*itemsize would be correct it may fail, e.g. a list reports its itemsize as zero, even though each list item consumes four bytes (on a 32-bit system). I don't really see a problem with calling it sizeof, so I would then propose sys.sizeof as the appropriate location. -- nosy: +loewis __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Raymond Hettinger [EMAIL PROTECTED] added the comment: Proposals like this have been rejected in the past. Memory consumption is an evasive concept. Lists over-allocate space, there are freelists, there are immortal objects, the python memory allocator may hang-on to space thought to be available, the packing and alignment of structures varies across implementations, the system memory allocator may assign much larger chunks than are needed for a single object, and the memory may not be freed back to the system. Because of these issues, it is not that meaningful to say the object x consumes y bytes. -- nosy: +rhettinger __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Martin v. Löwis [EMAIL PROTECTED] added the comment: Proposals like this have been rejected in the past. Memory consumption is an evasive concept. Lists over-allocate space That issue is addressed in this patch. there are freelists, but they allocate just an upper bound. there are immortal objects, the python memory allocator may hang-on to space thought to be available These issues are orthogonal to the memory consumption of a single object. the packing and alignment of structures varies across implementations This is addressed in the current patch. the system memory allocator may assign much larger chunks than are needed for a single object While true in general, this is not true in practice - in particular, when objects get allocated through pymalloc. and the memory may not be freed back to the system. Because of these issues, it is not that meaningful to say the object x consumes y bytes. This is not true. It is meaningful to say that (and many that you noted are independent from such a statement, as they say things for the whole interpreter, not an individual object). The patch meets a real need, and is the minimum amount of code that actually *has* to be implemented in the virtual machine, to get a reasonable analysis of the total memory consumption. Please be practical here, not puristic. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2900] math.copysign(1, float('nan'))
New submission from Christian Heimes [EMAIL PROTECTED]:
What's your opinion on the edge case
math.copysign(1, float('nan'))
1.0
Is 1.0 the correct answer? IMHO Nan would be better ...
--
assignee: marketdickinson
components: Extension Modules
messages: 66997
nosy: christian.heimes, marketdickinson
priority: normal
severity: normal
status: open
title: math.copysign(1, float('nan'))
type: behavior
versions: Python 2.6, Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2900
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2900] math.copysign(1, float('nan'))
Mark Dickinson [EMAIL PROTECTED] added the comment:
This is fine. copysign isn't supposed to propagate NaNs---it's just
supposed to silently transfer the sign bit from the second argument to the
first. So I think this is correct behaviour.
Incidentally, on OS X:
from math import copysign
copysign(1, float('nan'))
-1.0
This is also fine, IMO. It just so happens that on OS X the 'default' NaN
has its sign bit set.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2900
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2839] Moving lib-tk to tkinter package
Georg Brandl [EMAIL PROTECTED] added the comment: Committed modmerge patch in r63408. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2839 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1362475] Text.edit_modified() doesn't work
Matthias Kievernagel [EMAIL PROTECTED] added the comment: Hi Guilherme, funny, I wasn't aware of this duplicate of this issue until I got the message of your comment :) The other duplicate is: http://bugs.python.org/issue1643641 which was closed by Georg Brandl upon my request. The oldest issue is: http://bugs.python.org/issue961805 Both these issues have my patch attached. (it's somewhat resembling yours and the proposition of Ron Provost - except that it is 1.5 years older) The latter issue also has demo code attached. Can someone close this one or the other open issue?? Cheers, Matthias Kievernagel _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1362475 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1362475] Text.edit_modified() doesn't work
Guilherme Polo [EMAIL PROTECTED] added the comment: Closed as this is yet another duplicate. -- resolution: - duplicate status: open - closed superseder: - Text.edit_modified() fails _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1362475 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2868] Problem with urllib and urllib2 in urlopen?
Martin McNickle [EMAIL PROTECTED] added the comment: I verified the behaviour but this is a problem with that particular site, not with urllib/urllib2. Should be closed. -- nosy: +BitTorment __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2868 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue961805] Text.edit_modified() fails
Guilherme Polo [EMAIL PROTECTED] added the comment: From issue 1362475: This bug still exists, I'm attaching a patch against current python-trunk. This patch is based on the fact that documentation tk 8.4 (version which edit command was added) and tk 8.5 says only edit_modified is supposed to return something, which is either 0 or 1, so there was no reason to use _gettints on that tk.call, and returning an empty tuple is against the expected value, 0. --- cut --- This message and patch is almost a duplicate of Matthias, just updating from the just closed, and duplicated, issue 1362475 -- keywords: +patch nosy: +gpolo Added file: http://bugs.python.org/file10355/edit_modified.diff Tracker [EMAIL PROTECTED] http://bugs.python.org/issue961805 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue837234] Tk.quit and sys.exit cause Fatal Error
Matthias Kievernagel [EMAIL PROTECTED] added the comment: Hi, found a related (duplicate ?) issue which mentions a platform and has code producing the error: http://bugs.python.org/issue775544 Can someone based on WinXP try the code? Attaching it here for easier reference. Works without problem on my Linux 2.6, Python 2.4.1 with Tk 8.4 Guess the other issue is similar enough to close it. Regards, Matthias Kievernagel -- nosy: +mkiever Added file: http://bugs.python.org/file10356/issue775544.py Tracker [EMAIL PROTECTED] http://bugs.python.org/issue837234 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2819] Full precision summation
Mark Dickinson [EMAIL PROTECTED] added the comment: Okay, just to show it's possible: Here (msum4.py) is a modified version of Raymond's recipe that deals correctly with: (1) intermediate overflows (2) special values (infs and nans) in the input, and (3) always gives correctly rounded results. The file contains more tests, and a proof of correctness. The algorithm still makes only a single pass through the given iterable, and there should be minimal slowdown in the common case. It's still only 60-70 lines of Python code, so I don't think it would be unreasonable to aim to include these modifications in the C version. Added file: http://bugs.python.org/file10357/msum4.py __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2819 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2868] Problem with urllib and urllib2 in urlopen?
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2868 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2899] Fixers find, rfind, etc in 'string' module
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- title: Fixes find, rfind, etc in 'string' module - Fixers find, rfind, etc in 'string' module __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2899 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue961805] Text.edit_modified() fails
Georg Brandl [EMAIL PROTECTED] added the comment: OK, committed patch as r63412. -- nosy: +georg.brandl resolution: - fixed status: open - closed Tracker [EMAIL PROTECTED] http://bugs.python.org/issue961805 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2337] Backport oct() and hex() to use __index__
Georg Brandl [EMAIL PROTECTED] added the comment: The warning message for oct() should include that the output will be different too. Else this is fine with me. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2337 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Georg Brandl [EMAIL PROTECTED] added the comment: Lists will need a custom tp_footprint then, too. Or, if we call it sizeof, the slot should be tp_sizeof. BTW, is a new slot necessary, or can it just be a type method called __sizeof__? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2839] Moving lib-tk to tkinter package
Guilherme Polo [EMAIL PROTECTED] added the comment: Patch added for handling the merging of tkSimpleDialog into tkinter.simpledialog and tkFileDialog into tkinter.filedialog, specific for py3k. Added file: http://bugs.python.org/file10358/tkinter_modmerge_py3k.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2839 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Martin v. Löwis [EMAIL PROTECTED] added the comment: Lists will need a custom tp_footprint then, too. True. BTW, is a new slot necessary, or can it just be a type method called __sizeof__? It wouldn't be a type method, but a regular method on the specific type, right? I think that would work as well. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2839] Moving lib-tk to tkinter package
Georg Brandl [EMAIL PROTECTED] added the comment: Handled Py3k branch in revs 63417 to 63423. Closing this issue. -- resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2839 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2337] Backport oct() and hex() to use __index__
Benjamin Peterson [EMAIL PROTECTED] added the comment: Done in r63425. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2337 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2349] Py3K warn against assigning to True/False
Benjamin Peterson [EMAIL PROTECTED] added the comment: I'm attaching a new patch with changes made from the Georg's comments. Added file: http://bugs.python.org/file10359/bool_assign6.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2349 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2337] Backport oct() and hex() to use __index__
Benjamin Peterson [EMAIL PROTECTED] added the comment: I have reverted this. See mail.python.org/pipermail/python-checkins/2008-May/069843.html. -- resolution: fixed - status: closed - pending __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2337 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2337] Backport oct() and hex() to use __index__
Changes by Eric Smith [EMAIL PROTECTED]: -- nosy: +eric.smith __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2337 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2898] Add memory footprint query
Raymond Hettinger [EMAIL PROTECTED] added the comment: Guido, recently you've been opposed to adding more slots. Any opinions on this one? Also, is this something you want an additional builtin for? -- assignee: - gvanrossum nosy: +gvanrossum __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2898 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2353] Use of file.xreadlines() should raise a Py3K warning
Georg Brandl [EMAIL PROTECTED] added the comment: Committed slightly reviewed patch and test in r63340. -- nosy: +georg.brandl resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2353 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2901] error: can't allocate region from mmap() when receiving big chunk of data
Håkan Waara [EMAIL PROTECTED] added the comment: test_server.py and test_client.py zipped attached. Added file: http://bugs.python.org/file10360/testcase.zip __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2901 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2901] error: can't allocate region from mmap() when receiving big chunk of data
New submission from Håkan Waara [EMAIL PROTECTED]: I'm using the standard lib SimpleXMLRPCServer to receive a file from a client. The file is sent using an instance of the xmlrpclib.Binary class. Whenever the file is bigger than a few MB, the server reports spews out an internal error to stderr: Python(13950) malloc: *** mmap(size=9916416) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug This *only* happens if the client and server are not the same machine; i.e., connecting and sending to localhost always works. Attached testcase: * test_server.py opens a server on port 8001 waiting to receive a blob of data over HTTP. * Modify test_client.py to point at a big file, and then connect to the server machine, and you will ses the error. I'm running OS X-bundled Python 2.5.1 on OS X 10.5.2 -- messages: 67018 nosy: hwaara severity: normal status: open title: error: can't allocate region from mmap() when receiving big chunk of data versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2901 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2901] error: can't allocate region from mmap() when receiving big chunk of data
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- type: - crash __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2901 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2902] tkinter uses MacOS
New submission from Benjamin Peterson [EMAIL PROTECTED]: A few days ago I removed the MacOS module. I didn't realize that it was used in Tkinter until today. It seems the module is only used in one spot: if _MacOS and hasattr(_MacOS, 'SchedParams'): # Disable event scanning except for Command-Period _MacOS.SchedParams(1, 0) # Work around nasty MacTk bug # XXX Is this one still needed? self.update() Is this still needed? If so, this check will have to integrated into _tkinter. -- messages: 67020 nosy: benjamin.peterson priority: critical severity: normal status: open title: tkinter uses MacOS type: behavior versions: Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2902 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2819] Full precision summation
Jean Brouwers [EMAIL PROTECTED] added the comment: I intend to submit a C version of msum4 shortly. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2819 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2903] Add __name__ in globals of generated namedtuple namespace
New submission from Guillaume Knispel [EMAIL PROTECTED]: Some 3rd party tracers rely on frame.f_globals[__name__] to be set to the module name that contains the code currently executed. frame.f_globals[__name__] is not defined when some code has been generated with exec, which is the way namedtuples are created. The attached patch set __name__ to '__generated_%s__' % typename in the generated namespace, which is quite handy to see where the code comes from. Indeed if sys._getframe is available it sets __name__ to '__generated_%s__%s__' % (typename, result.__module__) which is even more useful. -- components: Library (Lib) files: collections.r59898.patch keywords: patch messages: 67022 nosy: xilun severity: normal status: open title: Add __name__ in globals of generated namedtuple namespace versions: Python 2.6 Added file: http://bugs.python.org/file10361/collections.r59898.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2903 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2904] Cross-referencing to a method using an alternate title don't work with add_function_parentheses=True
New submission from Leandro Lucarella [EMAIL PROTECTED]: When using cross-references to a method using an alternate title, like :meth:`some title some_method` and configuration option add_function_parentheses is True, the link is not generated (if this option is False, it works fine. -- assignee: georg.brandl components: Documentation tools (Sphinx) messages: 67023 nosy: georg.brandl, llucax severity: normal status: open title: Cross-referencing to a method using an alternate title don't work with add_function_parentheses=True type: behavior versions: 3rd party __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2904 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
