[issue2249] To document assertTrue in unittest
New submission from Jesús Cea Avión: Python 2.4 and 2.5 unittest includes a assertTrue method undocumented. Document it. It is the same method as assert_ and failUnless, but the name seems clearer. -- assignee: georg.brandl components: Documentation messages: 63347 nosy: georg.brandl, jcea severity: minor status: open title: To document assertTrue in unittest versions: Python 2.5, Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2249 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2249] To document assertTrue in unittest
Changes by Jesús Cea Avión: -- versions: +Python 2.4 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2249 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2222] Memory leak in os.rename?
Hirokazu Yamamoto added the comment: Alexander, I've looked into Python/getargs.c, I think posix_2str code is fine. (PyArg_ParseTuple with format et) After conversion succeeded on path1, addcleanup() adds memory buffer for path1 into freelist. When error happend on path2, its memory will be freed on cleanreturn(). __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1092502] Memory leak in socket.py on Mac OS X
Changes by vila: -- nosy: +vila _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1092502 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1389051] imaplib causes excessive fragmentation for large documents
Changes by vila: -- nosy: +vila _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1389051 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2196] Fix hasattr's exception problems
Paul Pogonyshev added the comment: I think it would be better not to hardcode specific 2 exceptional cases and indeed follow that second way of instanceof(..., Exception). I think it was introduced exactly to separate things that can be caught by default from things that may be caught only in very special cases. I don't find it good Python interpreter not following its own rules. -- nosy: +_doublep __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2196 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2251] tarfile using nonexistent function
New submission from Goten Xiao: Steps to reproduce: Create test.py with the following contents: tar = tarfile.open(test.tar, w) tar.addfile(testdir) tar.close() Run the following commands (or equivalent on alternative platforms): mkdir testdir touch testdir/testfile python test.py Resultant output: Traceback (most recent call last): File test.py, line 4, in module tar.addfile(testdir) File /usr/lib/python2.5/tarfile.py, line 1492, in addfile buf = tarinfo.tobuf(self.posix) AttributeError: 'str' object has no attribute 'tobuf' Tested on Python 2.5.1 and 2.5.2 from slackware-current packages. -- components: Library (Lib) messages: 63351 nosy: GotenXiao severity: major status: open title: tarfile using nonexistent function type: crash versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2251 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2251] tarfile using nonexistent function
Goten Xiao added the comment: Whoops, add: import tarfile to the top of test.py. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2251 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2179] with should be as fast as try/finally
Nick Coghlan added the comment: Patch applied cleanly for me and all tests pass. It also looked good on a visual scan over the diff text. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2251] tarfile using nonexistent function
Lars Gustäbel added the comment: This is in fact misuse of the addfile() method on your side. The docs (http://docs.python.org/dev/library/tarfile.html#tarfile.TarFile.addfile) state that the first argument is supposed to be a TarInfo object not a pathname. You should use the add() method instead. -- assignee: - lars.gustaebel nosy: +lars.gustaebel resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2251 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2179] with should be as fast as try/finally
Nick Coghlan added the comment: I went ahead and committed the change to the bytecode generation as r61290. The deficiencies in the lock implementation should probably be raised as a separate issue, so I'm closing this one. -- resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2179] with should be as fast as try/finally
Amaury Forgeot d'Arc added the comment: Hm, my tests do not see any speedup with this patch. I used VS2005 on win2K, and VS2008 on winXP. Timings are very similar before and after this patch. Maybe the optimization is only useful with gcc? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2222] Memory leak in os.rename?
Alexander Belopolsky added the comment: Aha! I did not know about the cleanup. Maybe that should be documented as well. This shows that using O with a converter returning a PyObject* is a bad idea. (General clean-up is not possible for O because there is no way to tell what type the converter returns.) I am still +1 on your original patch. It is obviously correct and fixes the bug with minimum of changes. However, win32 code in posixmodule.c needs some clean-up. convert_to_unicode should be eliminated in favor of the approach used in win32_1str. It may also make sense to move conversion/api selection code to a win32_2str function. Even if it will be only used for rename, it will make the code more readable by making win32 code structure similar to posix. All this is a topic for another issue. I believe the only thing that needs to be done here is to enable error case testing for all platforms in the unit test. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2240] setitimer, getitimer wrapper
Changes by Ralf Schmitt: -- nosy: +schmir __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2240 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()
Changes by Ralf Schmitt: -- nosy: +schmir __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2252] continue documentation
Changes by Ben Pfaff: -- assignee: georg.brandl components: Documentation nosy: blp, georg.brandl severity: normal status: open title: continue documentation versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2252 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2253] continue documentation internally inconsistent
New submission from Ben Pfaff: The continue documentation says: continue may only occur syntactically nested in a for or while loop, but not nested in a function or class definition or finally statement within that loop. In a footnote to that documentation, it says: The restriction on occurring in the try clause is implementor's laziness and will eventually be lifted. But the documentation doesn't say that continue may not occur in the try clause. So there is an internal inconsistency here. Either the sentence in the footnote is wrong and should be removed, or the main documentation for continue should say that continue may not occur in a try clause. -- assignee: georg.brandl components: Documentation messages: 63358 nosy: blp, georg.brandl severity: minor status: open title: continue documentation internally inconsistent versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2253 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2252] continue documentation
New submission from Ben Pfaff: Apologies for filing this issue report: I hit Enter at the wrong time. Issue 2253 was what I really meant to file. You can close this issue. Sorry about that. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2252 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.
Alexander Belopolsky added the comment: Your description of the patch is a bit misleading. As far as I can tell only the first chunk (Python/import.c changes) addresses a potential buffer overflow. For example the last chunk (Modules/posixmodule.c changes) simply eliminates an unused variable. While a worthwhile change, it should not be bundled with what is potentially a security patch. I have a few suggestions: 1. It will really help if you produce a test case that crashes the interpretor. I am sure that will get noticed. 2. If any of buffer overflows apply to the current production versions (2.4 or 2.5) or even the alpha release (2.6a1), it would make sense to backport it to the trunk. Once again, security issues in the trunk will get noticed much faster than in py3k branch. -- nosy: +belopolsky __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1950 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2252] continue documentation
Changes by Georg Brandl: -- resolution: - duplicate status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2252 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2254] Python CGIHTTPServer information disclosure
New submission from sumar: Summary: An information disclosure flaw exists in standard python CGIHTTPServer module. Bug is confirmed in python 2.5 @ fedora 7 (python-2.5-15.fc7). Description: Requesting cgi script (in example test.py) without / in the beginnig of URL cause return script content/code instead of script execution. It could lead to disclose some secret information eg. password. Exploit code: Connected to localhost. Escape character is '^]'. GET cgi-bin/test.py HTTP/1.0 HTTP/1.0 200 OK Server: SimpleHTTP/0.6 Python/2.5 Date: Fri, 07 Mar 2008 14:55:30 GMT Content-type: text/plain Content-Length: 150 Last-Modified: Fri, 07 Mar 2008 14:55:04 GMT #!/usr/bin/env python print 'Content-Type: text/html' print 'Cache-Control: no-cache' print print 'Hello' passwd='secret' path=/opt/myapp/secretpath Connection closed by foreign host. correct request: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GET /cgi-bin/test.py HTTP/1.0 HTTP/1.0 200 Script output follows Server: SimpleHTTP/0.6 Python/2.5 Date: Fri, 07 Mar 2008 15:01:03 GMT Content-Type: text/html Cache-Control: no-cache Hello Connection closed by foreign host. -- components: Library (Lib) messages: 63361 nosy: m.sucajtys severity: normal status: open title: Python CGIHTTPServer information disclosure type: security versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2254 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue771479] pyconfig.h duplicates common defines
Martin v. Löwis added the comment: None of the PACKAGE_ macros gets defined anymore. For the other ones, I'll close the report as won't fix. -- resolution: - wont fix status: open - closed Tracker [EMAIL PROTECTED] http://bugs.python.org/issue771479 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.
Alexander Belopolsky added the comment: I tried to produce a buffer overflow in get_parent (import.c), but an attempt to import a module with non-ascii characters is aborted in getargs.c before get_parent is reached: __import__(\u0080xyz) Traceback (most recent call last): File stdin, line 1, in module TypeError: __import__() argument 1 must be string without null bytes, not str This looks like a bug. At the very least the error message is misleading because there are no null bytes in \u0080xyz string. The offending code is if ((Py_ssize_t)strlen(*p) != PyUnicode_GetSize(arg)) return converterr(string without null bytes, arg, msgbuf, bufsize); at getargs.c:826 However, given the preceding XXX WH! comment, this is probably a sign of not yet implemented feature rather than a bug. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1950 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2254] Python CGIHTTPServer information disclosure
Guilherme Polo added the comment: I'm attaching a patch that fixes this, it was done for rev 61179 (trunk). Note that is_cgi method is incorrectly documented, even more now. Only the first line in its docstring is correct now, before this patch, last paragraph was correct too. -- keywords: +patch nosy: +gpolo Added file: http://bugs.python.org/file9628/CGIHTTPServer_is_cgi_fix.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2254 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2254] Python CGIHTTPServer information disclosure
Guilherme Polo added the comment: oops, I was doing some tests in the last patch and left a bug in it. I'm attaching a new one. Added file: http://bugs.python.org/file9629/CGIHTTPServer_is_cgi_fix2.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2254 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2196] Fix hasattr's exception problems
Benjamin Peterson added the comment: Here's a patch for that. Personally, I'm +1 on either option; I just want it fixed. :) I suppose the only (minor) problem with propagate things which are not Exception is libraries where the exceptions don't extend Exception. However, the ability to do this is being removed in Py3k, so it's not huge. Added file: http://bugs.python.org/file9630/hasattr_fixes2.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2196 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2196] Fix hasattr's exception problems
Benjamin Peterson added the comment: That last patch is malformed. Added file: http://bugs.python.org/file9631/hasattr_fixes2-real.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2196 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2254] Python CGIHTTPServer information disclosure
Guilherme Polo added the comment: This corrects is_cgi docstring (maybe this should be done in a new issue?). It also removes a part of it that I believe to not be necessary, someone correct me if I'm wrong. Added file: http://bugs.python.org/file9632/CGIHTTPServer_is_cgi_doc_fix.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2254 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.
Alexander Belopolsky added the comment: Here are my comments on the other parts of the patch: Python/structmember.c The existing code is safe, but would silently produce wrong result if T_CHAR attribute is assigned a non-ascii character. With the patch this situation will be detected and an exception raised. I am not sure that would be a desired behavior of py3k. I could not find any examples of using T_CHAR member in the stdlib, but an alternative solution would be to change T_CHAR code to mean PY_UNICODE_TYPE instead of char member. Objects/typeobject.c %s - .400s is an obviously good change. The existing __doc__ processing code is correct. Proposed code may be marginally faster, but will allow docstrings with embedded null characters, which may or may not be desirable (and may break other code that uses tp_doc). Finally PyUnicode_AsStringAndSize always returns null-terminated strings, so memcpy logic does not need to be altered. Objects/structseq.c Change from macros to enums is purely stylistic and python C style seem to favor macros. I don't think a repr of a python object can contain embedded null characters, but even if that were the case, the patched code would not support it because the resulting buffer is returned with PyUnicode_FromString(buf). Modules/datetimemodule.c Existing code compensates for an error in initial estimate of totalnew when it checks for overflow, but the proposed change will make code more efficient. Modules/zipimport.c Since 's' format unit in PyArg_ParseTuple does not properly support unicode yet, it is hard to tell if the current code is wrong, but unicode paths cannot have embedded null characters, so use of 's#' is not necessary. Modules/timemodule.c Supporting format strings with null characters is probably a good idea, but that would be an RFE rather than a bug fix. Modules/parsermodule.c Looks like there is a bug there. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1950 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2255] Change Mandrake by Mandriva for platform.dist()
New submission from Nicolas Lécureuil: here is a patch fixing the issue by changing mandrake to mandriva -- components: Library (Lib) files: python-2.5-change-mandrake.patch keywords: patch messages: 63370 nosy: neoclust severity: normal status: open title: Change Mandrake by Mandriva for platform.dist() type: behavior versions: Python 2.5 Added file: http://bugs.python.org/file9633/python-2.5-change-mandrake.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2255 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2249] To document assertTrue in unittest
Changes by Benjamin Peterson: -- nosy: +purcell __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2249 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2255] Change Mandrake by Mandriva for platform.dist()
Changes by Benjamin Peterson: -- nosy: +lemburg __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2255 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed
New submission from Jim Kleckner:
When I install 2.6a1 onto a Windoze machine I get a dialog:
There is a problem with this Windows Installer package.
A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor.
Note that it didn't have VS2008 or any other new code installed.
The problem appears related to Tkinter but that isn't clear.
When running the Python console, running
import Tkinter
results in an error saying that _tkinter can't be loaded.
DLL load failed. The system can't find _tkinter.pyd
_tkinter.pyd and tcl84.dll and tk84.dll are in DLLs and
appear to have reasonable permissions.
I suspect something in the install failed to set something
in the registry.
This is on a current-patch XP
system and that I also tried python-2.6.13944.msi
from the buildbot just in case after uninstalling/reinstalling
with no difference.
Attached is a compressed log of the install.
Perhaps this PROPERTY CHANGE: Deleting SECONDSEQUENCE
is the problem?
Here is an excerpt from the log file:
Property(S): Privileged = 1
Property(S): DATABASE = C:\WINDOWS\Installer\5f5ad0.msi
Property(S): OriginalDatabase = C:\cygwin\tmp\python-2.6a1.msi
Property(S): UILevel = 5
Property(S): Preselected = 1
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SOURCEDIR = C:\cygwin\tmp\
Property(S): SourcedirProduct = {0BA82E1B-52FD-4E03-8610-A6C76238E8A8}
Property(S): ProductToBeRegistered = 1
MSI (s) (FC:D0) [16:38:30:939]: MainEngineThread is returning 1603
MSI (s) (FC:C0) [16:38:30:939]: Destroying RemoteAPI object.
MSI (s) (FC:54) [16:38:30:939]: Custom Action Manager thread ending.
MSI (c) (E0:54) [16:38:30:954]: Back from server. Return value: 1603
MSI (c) (E0:54) [16:38:30:954]: Decrementing counter to disable
shutdown. If counter = 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (E0:54) [16:38:30:954]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
property. Its current value is '1'.
Action ended 16:38:30: ExecuteAction. Return value 3.
MSI (c) (E0:54) [16:38:30:954]: Doing action: FatalError
Action 16:38:30: FatalError.
Action start 16:38:30: FatalError.
Action 16:38:30: FatalError. Dialog created
Action ended 16:38:32: FatalError. Return value 2.
Action ended 16:38:32: INSTALL. Return value 3.
MSI (c) (E0:54) [16:38:32:375]: Destroying RemoteAPI object.
MSI (c) (E0:2C) [16:38:32:375]: Custom Action Manager thread ending.
Property(C): X = C:\Python26\Tools\pynche\X\
Property(C): UpgradeCode = {65E6DE48-A358-434D-AA4F-4AF72DB4718F}
Property(C): ProductName = Python 2.6a1
Property(C): ProductCode = {0BA82E1B-52FD-4E03-8610-A6C76238E8A8}
Property(C): ProductVersion = 2.6.101
Property(C): Manufacturer = Python Software Foundation
--
components: Installation
files: debuglog.txt.zip
messages: 63371
nosy: jkleckner
severity: normal
status: open
title: Install failure of 2.6a1 on Windows XP without VS8 installed
type: behavior
versions: Python 2.6
Added file: http://bugs.python.org/file9634/debuglog.txt.zip
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2256
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2255] Change Mandrake by Mandriva for platform.dist()
Facundo Batista added the comment: Assigning as the platform.py file says. The patch is straightforward, I'm only concerned with backward compatibility... -- assignee: - lemburg nosy: +facundobatista __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2255 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2179] with should be as fast as try/finally
Changes by Jesús Cea Avión: -- nosy: +jcea __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2218] Enhanced hotshot profiler with high-resolution timer
Jean Brouwers added the comment: Here is another version of the profiler files with 7 minor changes in the _hotshot.c file. Use this hires_version3 set, if any. Added file: http://bugs.python.org/file9635/hires_hotshot3.tgz __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2218 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2257] typo in tutorial section 4.4 - final break statement is missing
New submission from k-e-n: The code from section 4.4 of the tutorial follows. This code does not produce the output shown. Adding a final break statement will fix this. for n in range(2, 10): ... for x in range(2, n): ... if n % x == 0: ... print n, 'equals', x, '*', n/x ... break ... else: ... # loop fell through without finding a factor ... print n, 'is a prime number' ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 -- assignee: georg.brandl components: Documentation messages: 63374 nosy: Kyte999, georg.brandl severity: minor status: open title: typo in tutorial section 4.4 - final break statement is missing versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2257 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733184] slice type is unhashable
Alexander Belopolsky added the comment: Patch # 408326 was designed to make assignment to d[:] an error where d is a dictionary. See discussion starting at http://mail.python.org/pipermail/python-list/2001-March/072078.html . I think the only reason slice objects need to be comparable is only to suppress inheritance of the default hash from object. This RFE is ripe to be rejected. Slice objects are really meant to be internal structures and not passed around in the user's code. You can always use tuples instead of slices and convert the to slices with slice(*t) when needed. -- nosy: +belopolsky type: - feature request _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1733184 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1617161] Instance methods compare equal when their self's are equal
Alexander Belopolsky added the comment: the change was meant to unify the behavior of built-in and user method objects I don't think it achieved that. Consider: [].index == [].index False but UserList().index == UserList().index True -- nosy: +belopolsky _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1617161 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1741218] string formatter %x problem with indirectly given long
Alexander Belopolsky added the comment: This issue has been resolved in issue1742669 . $ ./python.exe Python 2.6a1+ (trunk:61230M, Mar 4 2008, 10:56:31) [GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin Type help, copyright, credits or license for more information. class X: ... def __int__(self): return 0x8000 ... %08x % X() '8000' -- nosy: +belopolsky, facundobatista title: string formatter %x problem with indirectly given long - string formatter %x problem with indirectly given long _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1741218 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2257] typo in tutorial section 4.4 - final break statement is missing
Changes by Raymond Hettinger: -- assignee: georg.brandl - rhettinger nosy: +rhettinger __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2257 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1741218] string formatter %x problem with indirectly given long
Facundo Batista added the comment: Already fixed. Thanks Kenji for the report, Gabriel for the patch in the other issue, and Alexander for noticing this duplicateness. -- resolution: - duplicate status: open - closed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1741218 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733184] slice type is unhashable
Raymond Hettinger added the comment: Guido, any thoughts? I'm +0 on making slices hashable -- no real harm from doing it -- not much benefit either. -- assignee: - gvanrossum nosy: +gvanrossum _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1733184 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733184] slice type is unhashable
Alexander Belopolsky added the comment: In case I did not make my position clear in my previous post, I am -1 on this RFE. x[:] should mean slicing, not getitem. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1733184 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733184] slice type is unhashable
Jean-Paul Calderone added the comment: Slice objects are really meant to be internal structures and not passed around in the user's code. I don't know what they're meant to be, but they're certainly not internal. If you implement __getitem__, __setitem__, or __delitem__, then chances are Python is going to be passing slices to your code. That doesn't sound internal to me. Having hashable slices is nice. The repr() workaround has a major drawback in that it makes it difficult to use the extremely useful indices method of the slice type. -- nosy: +exarkun _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1733184 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2249] To document assertTrue in unittest
Raymond Hettinger added the comment: I prefer that this remain undocumented. The published API is already too fat. This would make it fatter without adding functionality. -- nosy: +rhettinger __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2249 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed
Michael Urman added the comment: The failure is signaled by the return code from the call to compileall.py: MSI (s) (FC:D0) [16:38:27:394]: Note: 1: 1722 2: CompilePyc 3: C:\Python26\python.exe 4: -Wi C:\Python26\Lib\compileall.py -f -x bad_coding|badsyntax|site-packages C:\Python26\Lib The install succeeds anyway because this is after InstallFinalize. That makes this a wart that will likely fail similarly on Vista under UAC (if not already handled by being conditioned out). This should probably be a scheduled between InstallFiles and InstallFinalize with inscript+noimpersonate. -- nosy: +michaelurman __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2256 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1733184] slice type is unhashable
Guido van Rossum added the comment:
Alexander nailed my motivation.
Have the proponents for this change really thought through that making
slices hashable means that henceforth this code will work?
d = {}
d[:] = [1, 2, 3] # surprise here
print d # prints {slice(None, None, None): [1, 2, 3]}
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1733184
_
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
