[issue11436] Clarify struct doc for format 's', when it is mentioned without numeric prefix

Terry J. Reedy added the comment: Those others field types have a standard or system-dependent fixed size and a number is an optional repeat count. Format 's' is always a single field because number prefix for that is special -- a field size. "For the 's' format character, the count is interp

[issue12014] str.format parses replacement field incorrectly

Changes by Ben Wolfson : Removed file: http://bugs.python.org/file22599/strformat-just-identifiers-please.diff ___ Python tracker ___ ___ Pyt

[issue12014] str.format parses replacement field incorrectly

Ben Wolfson added the comment: (same as previous) -- Added file: http://bugs.python.org/file22602/strformat-just-identifiers-please.diff ___ Python tracker ___

[issue12014] str.format parses replacement field incorrectly

Changes by Ben Wolfson : Removed file: http://bugs.python.org/file22598/strformat-as-documented.diff ___ Python tracker ___ ___ Python-bugs-li

[issue12014] str.format parses replacement field incorrectly

Ben Wolfson added the comment: undo integer -> decimalinteger in docs -- Added file: http://bugs.python.org/file22601/strformat-as-documented.diff ___ Python tracker ___ ___

[issue12510] IDLE get_the_calltip mishandles raw strings

New submission from Roy Fox : Hi, When you type (not copy-paste!) into an IDLE shell a string literal followed by ( you get a calltip. When the string contains a bad unicode escaping you get an error (see example below), which makes some sense. But when the string is raw, it isn't treated as

[issue12508] Codecs Anomaly

Changes by Raymond Hettinger : -- priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue12509] test_gdb fails on debug build when builddir != srcdir

New submission from Dave Malcolm : test_gdb.py fails when builddir != srcdir: the regex tries to match lines like this: #0 builtin_id (self=, v=()) at ../Python/bltinmodule.c:919 but isn't expecting the "../" before the "Python/bltinmodule.c" 2.7 uses a different regexp, and I don't think

[issue12014] str.format parses replacement field incorrectly

Raymond Hettinger added the comment: Please stick with "integer" instead of "decimalinteger". In an effort to make the docs more precise, there is an unintended effect of making them harder to understand. -- nosy: +rhettinger ___ Python tracker

[issue12014] str.format parses replacement field incorrectly

Ben Wolfson added the comment: And here is a patch for Greg Ewing's proposal: http://mail.python.org/pipermail/python-dev/2011-June/111934.html Again, decimal integers rather than any kind of integers are used. Both patches alter the exceptions expected in various places in test_unicode's te

[issue12508] Codecs Anomaly

STINNER Victor added the comment: You should use the io module, it doesn't have the bug :) -- ___ Python tracker ___ ___ Python-bugs-

[issue12508] Codecs Anomaly

STINNER Victor added the comment: I confirm, there is a bug in codecs.StreamReader. -- nosy: +haypo ___ Python tracker ___ ___ Python

[issue12508] Codecs Anomaly

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12014] str.format parses replacement field incorrectly

Ben Wolfson added the comment: This patch differs from the previous one; its goal is to bring the actual behavior of the interpreter into line with the documentation (with the exception of using only decimal integers, rather than any integers, wherever the documentation for str.format current

[issue12508] Codecs Anomaly

New submission from Saul Spatz : The attached script produces the output 'A\ufffdBC\ufffd' 'A\ufffdBC' although it seems to me that both lines should be the same. The first line is correct, I think, since the at the end is a maximal subpart of an ill-formed subsequence, according to the de

[issue12178] csv writer doesn't escape escapechar

Changes by Catalin Iacob : -- keywords: +patch Added file: http://bugs.python.org/file22596/0eb420ce6567.diff ___ Python tracker ___ _

[issue12178] csv writer doesn't escape escapechar

Catalin Iacob added the comment: I looked at this and tried to provide a patch + tests. Please review. The bug is that a writer can use writerow on some input data but if a reader with the same dialect reads them back they are different from the input ones. This happens when the input data co

[issue12507] tkSimpleDialog problem

Ned Deily added the comment: The problem is not with Python 2.7 per se. It's a problem when running on OS X with a Python linked with the current Aqua Cocoa Tk 8.5, such as the ActiveState Tcl/Tk. Your test case works OK when using the current 32-bit-only Python 2.7.2 from python.org which l

[issue12505] python interpreter not handle wildards properly

Changes by Brian Curtin : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker ___ __

[issue12198] zipfile.py:1047: DeprecationWarning: 'H' format requires 0 <= number <= 65535

Petri Lehtinen added the comment: Setting as duplicate of #6090. -- resolution: -> duplicate status: open -> closed superseder: -> zipfile: Bad error message when zipping a file with timestamp before 1980 ___ Python tracker

[issue6090] zipfile: Bad error message when zipping a file with timestamp before 1980

Changes by Petri Lehtinen : -- title: zipfile: Bad error message when zipping a with timestamp before 1980 -> zipfile: Bad error message when zipping a file with timestamp before 1980 ___ Python tracker ___

[issue6090] zipfile: Bad error message when zipping a with timestamp before 1980

Petri Lehtinen added the comment: Retitled to reflect that the error message should be enhanced. Attached a patch for 2.7 that raises ValueError for timestamps before 1980, documents that 1980 or later is required, and adds some tests. -- keywords: +needs review, patch nosy: +petri.le

[issue12505] python interpreter not handle wildards properly

yoch added the comment: Okay. Thanks :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12505] python interpreter not handle wildards properly

Sebastian Ramacher added the comment: That is definitely not python's job. That is the duty of your shell and python should never expand that. And it would lead to platform specific behavior as one can see with the following script: import sys import subprocess if __name__ == "__main__":

[issue12507] tkSimpleDialog problem

Changes by LMO : -- assignee: -> ronaldoussoren components: +Macintosh -Tkinter nosy: +ronaldoussoren ___ Python tracker ___ ___ Pyth

[issue12507] tkSimpleDialog problem

LMO added the comment: I confirmed that the problem does not exist under Win XP using python 2.7.2. -- ___ Python tracker ___ ___ Pyt

[issue12503] "with" statement error message is more confusing in Py2.7

Benjamin Peterson added the comment: The message is not inaccurate, but indeed misleading. In wonder what to do considering the traditional message of AttributeError is simply the missing attribute. -- nosy: +benjamin.peterson priority: normal -> low _

[issue12505] python interpreter not handle wildards properly

Eric V. Smith added the comment: > I dont't know. But what difference does it make, after all? I just want to make sure it's something that happens automatically and wouldn't require a change to python's C code. To the other point, someone who currently uses: python '*' would need to change t

[issue12505] python interpreter not handle wildards properly

yoch added the comment: With cmd and program compiled with setargv.obj, 'command *' is expanded, but not 'command "*"'. So, it's possible to escape them normally. [q] While it might be a separate .obj file, I believe it's still part of the logical C runtime that gets invoked before python's m

[issue12505] python interpreter not handle wildards properly

Eric V. Smith added the comment: I'm not suggesting they use cygwin. I'm saying that if they do use cygwin that something they currently do would stop working. There would be no way to pass a command line parameter of "*" to python, at least without adding more escaping (hard to say, document

[issue12505] python interpreter not handle wildards properly

yoch added the comment: 'setargv.obj' not C runtime, it's only static library to allow expanding wildcards arguments received by the program. (MinGW uses approximately the same principle for executables compilation) And, it's not appropriate to tell people who need this feature (arguments ex

[issue12505] python interpreter not handle wildards properly

Eric V. Smith added the comment: Both of them work under cygwin. My point is that neither would work if the C runtime expanded command line arguments. -- ___ Python tracker ___

[issue12507] tkSimpleDialog problem

LMO added the comment: Omitted platform info: MacBook Pro, 2.4 GHz Intel Core 2 Duo, 4 GB RAM, OS X 10.7 build 11A511 also confirmed on OS X 10.6 (Snow Leopard) -- ___ Python tracker __

[issue12507] tkSimpleDialog problem

New submission from LMO : tkSimpleDialog displays blank rectangle and hangs with version 2.7. Works fine on version 2.6. In attached program, click on button labeled "Press this Button" which will call tkSimpleDialog. -- components: Tkinter files: ACSDtest.py messages: 139939 nosy: r

[issue12505] python interpreter not handle wildards properly

yoch added the comment: Escape the wildcard like '*' will work (like on Linux). I think \* will not work... -- ___ Python tracker ___ __

[issue12505] python interpreter not handle wildards properly

Eric V. Smith added the comment: But what if you don't want the expansion done? I always invoke python from cygwin's bash shell, and sometimes I tell the shell not to expand the arguments, such as: python \* or python '*' I wouldn't want python (or rather the C runtime) to do the expansion i

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: Yeah, the reason my originally proposed semantics were wrong is because copying (or slicing) a memoryview object and then explicitly releasing that object would always fail through no fault of that code. That would be broken and the only way to fix it is to all

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: Le mercredi 06 juillet 2011 à 12:39 +, Stefan Krah a écrit : > Antoine, was this roughly your suggestion? I think so (!), but I also agree with Nick that raising BufferError when calling release() on a memoryview with exports is a reasonable alternative. -

[issue12506] NIS module cant handle multiple NIS map entries for the same GID

New submission from bjorn lofdahl : I think i have found an issue with the module that is only visible on larger sites that are using multiple group entries for the same group in the NIS maps. This comes from the bug that NIS can only handle 1024 chars per line, so if a group has more members

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Stefan Krah added the comment: [The first part of the message again, this time via the web interface.] Antoine is right, this needs to be fixed. I think that for *practical* purposes, the existing release() method already behaves like a tryrelease() method: >>> b = bytearray(b'123456789') >>>

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Stefan Krah added the comment: Antoine is right, this needs to be fixed. I think that for *practical* purposes, the existing release() method already behaves like a tryrelease() method: Traceback (most recent call last): File "", line 1, in BufferError: Existing exports of data: object canno

[issue11277] Crash with mmap and sparse files on Mac OS X

Changes by Steffen Daode Nurpmeso : Removed file: http://bugs.python.org/file22281/11277.apple-fix-2.diff ___ Python tracker ___ ___ Python-bu

[issue11277] Crash with mmap and sparse files on Mac OS X

Steffen Daode Nurpmeso added the comment: So sorry that i'm stressing this, hopefully it's the final message. Apples iterative kernel-update strategy resulted in these versions: 14:02 ~/tmp $ /usr/sbin/sysctl kern.version kern.version: Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 P

[issue12505] python interpreter not handle wildards properly

New submission from yoch : Hi, I'm using sys.argv to retrieve files and process them on the command line. Wildcards arguments (like : test.py *.txt) works fine under Linux (expanded), but not on Windows. It also affects the fileinput functions. The solution is to change the compilation options

[issue6721] Locks in python standard library should be sanitized on fork

Nir Aides added the comment: > Would you like to work on a patch to add an atfork mechanism? I will start with an attempt to generate a summary "report" on this rabbit hole of a problem, the views and suggestions raised by people here and what we may expect from atfork approach, its limitatio

[issue12493] subprocess: Popen.communicate() doesn't handle EINTR in some cases

STINNER Victor added the comment: > Out of curiosity, how could SIGALRM be missing on a Unix system? It is only missing on Windows. -- ___ Python tracker ___ __

[issue11436] Clarify struct doc for format 's', when it is mentioned without numeric prefix

Senthil Kumaran added the comment: That is for the string formatting character, correct? In this issue, we are talking about format character for struct and not just 's' but 'c','h','b','i' all without numeric prefix imply single value. -- ___ Pytho

[issue11436] Clarify struct doc for format 's', when it is mentioned without numeric prefix

Terry J. Reedy added the comment: A default of 1 in not implicit for output formatting. %s and {:s} mean however long needed, not %1s or {:1s} -- versions: -Python 3.1 ___ Python tracker _