[issue6392] IDLE 3.1 will not open

New submission from Matt : IDLE will not open; it does not give an error or even appear on the process list. I am using Windows XP on an IBM Thinkpad. I tried the prescribed solution on Issue 4049, and it returned this message: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 M

[issue5388] Green-box doc glitch: winhelp version only

Terry J. Reedy added the comment: Same path to python31.chm. I presume color difference is due to difference selections in Display Properties / Appearance tab. When I left- or right-click on upper-left icon as depicted in screen capture, choices are move, resize, , close, About HTML Help. N

[issue5555] optparse: clarify option concatenation in docs

Changes by Greg Ward : -- title: optparse -> optparse: clarify option concatenation in docs ___ Python tracker ___ ___ Python-bugs-list

[issue5555] optparse

Greg Ward added the comment: > This is an edited-down excerpt form the optparse documentation from: > > http://docs.python.org/library/optparse.html > > "... the traditional Unix syntax is a hyphen (“-“) followed by a > single letter [...] Some other option syntaxes that the world has seen in

[issue1571184] Generate numeric/space/linebreak from Unicode database.

Amaury Forgeot d'Arc added the comment: Here is a refreshed version of the patch, without the generated files. The patch combines several changes which are fairly independent from each other: - Using the unicode database to generate the functions adds 143 new codepoints to PyUnicode_ToNumeric

[issue6326] Add a "swap" method to list

Kristján Valur Jónsson added the comment: fyi, here is the thread from python-ideas: http://mail.python.org/pipermail/python-ideas/2009-June/005042.html The parallel to C++´s future "rvalue reference" is interesting (http://www.artima.com/cppsource/rvalue.html, see the "move" application)

[issue6326] Add a "swap" method to list

Adam Olsen added the comment: Fix it at its source: patch your database engine to use the type you want. Or wrap the list without subclassing (__iter__ may be the only method you need to wrap). Obscure performance hacks don't warrant language extensions. -- nosy: +Rhamphoryncus _

[issue5388] Green-box doc glitch: winhelp version only

Ezio Melotti added the comment: This is what I see here (see attached image). The only scrollbar is the one at the bottom for the whole page. The file is under Start -> Programs -> Python 3.1 -> Python Manuals, and the path/file is C:\Programs\Python31\Doc\python31.chm (you can see it right-clic

[issue6312] httplib fails with HEAD requests to pages with "transfer-encoding: chunked"

Changes by Ezio Melotti : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue1571184] Generate numeric/space/linebreak from Unicode database.

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

[issue6391] Incorrect description of unittest.TestCase.run

Ezio Melotti added the comment: Fixed in r73712. I left "result object" because the object can also be a subclass of TestResult. I also changed the last part to clarify that the result object is never returned to the caller, even when it's passed to run(). Thanks! -- resolution: -> fi

[issue1571184] Generate numeric/space/linebreak from Unicode database.

Vernon Cole added the comment: Adding Python 2.6 to the list of affected versions - as that is where I found the bug reported in issue 6383 (now superseded by this one.) -- nosy: +vernondcole versions: +Python 2.6, Python 3.0 ___ Python tracker

[issue5801] spurious empty lines in wsgiref code

Pablo Torres Navarrete added the comment: Oops, forgot to add the .diff extension so web browsers don't get confused. Their contents are the same though. -- keywords: +patch Added file: http://bugs.python.org/file14411/wsgiref-patch.diff ___ Python

[issue5801] spurious empty lines in wsgiref code

Pablo Torres Navarrete added the comment: The patch applies to rev 73702 of the py3k branch. -- ___ Python tracker ___ ___ Python-bugs

[issue5801] spurious empty lines in wsgiref code

Pablo Torres Navarrete added the comment: I cleaned the rest of the module by shortening lines that are too long, removing useless blocks of empty lines and adding whitespace around operators and after commas. Nothing in the programming logic was changed. -- Added file: http://bugs.pyt

[issue6391] Incorrect description of unittest.TestCase.run

Ezio Melotti added the comment: >>> class MyTest(TestCase): ... def runTest(self): pass ... def defaultTestCase(self): ... print('defaultTestCase called') ... >>> test = MyTest() >>> test.run() >>> class MyTest(TestCase): ... def runTest(self): pass ... def defaultTestResult(self): .

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: Yes, my patch is entirely contained in the one from issue1571184. I mark this one as a duplicate, and will review and update the other. -- dependencies: -Generate numeric/space/linebreak from Unicode database. resolution: -> duplicate status: op

[issue6391] Incorrect description of unittest.TestCase.run

New submission from En-Ran Zhou : In Python 2.6 Document, Library reference 26.3 unittest (http://docs.python.org/library/unittest.html#unittest.TestCase.run) The description of TestCase.run method says that ``If result is omitted or None, a temporary result object is created (by calling the defa

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Martin v. Löwis added the comment: Notice that this is a duplicate of the longstanding issue1571184, which has a patch that is more comprehensive than the one proposed here. So rather than accepting Amaury's patch, I'd prefer to see Anders' patch reviewed, and revised as necessary. -- d

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Vernon Cole added the comment: Wow! Quick response! My outstanding bug on IronPython has been hanging out there since August of last year. I don't really want to try compiling the standard library on my laptop, but I do want to fully test my code soon. What is the first place I can expect to s

[issue5331] multiprocessing hangs when Pool used within Process

Jesse Noller added the comment: Committed in r73708 on trunk -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue5155] Multiprocessing.Queue created by sub-process fails when used in sub-sub-process ("bad file descriptor" in q.get())

Jesse Noller added the comment: Committed in r73708 on trunk -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

Jesse Noller added the comment: Committed in r73708 on trunk -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue6390] File reads past EOF in "w+b" mode

Amaury Forgeot d'Arc added the comment: Yes, see the discussion in issue3207, specially this part: http://www.cplusplus.com/reference/clibrary/cstdio/fopen.html """ For the modes where both read and writing (or appending) are allowed (those which include a "+" sign), the stream should be flushe

[issue6390] File reads past EOF in "w+b" mode

New submission from Brian Mearns : Open a file in "w+b" mode: if you write to the file, then read from it without seeking backward, it reads past the EOF, apparently out into memory, which could be a pretty bad security concern. Have not checked if "w+" mode does the same. ### Bad behavior... >>

[issue6371] Minor internal link errors in Optparse doc

Georg Brandl added the comment: Thanks, fixed in r73707. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue1388872] Polymorphic getters / setters

Amaury Forgeot d'Arc added the comment: This is normal behavior: the property is created with the functions created just above, even before they belong to any class. To make the property search the class hierarchy, you could write: foo = property(lambda x: x.get_foo(), lambda x, v: x.set_foo

[issue1367628] use PyOS_ReadlineFunctionPointer in non-interractive input

Amaury Forgeot d'Arc added the comment: Isn't the same functionality already implemented by code.interact()? -- nosy: +amaury.forgeotdarc resolution: -> rejected status: open -> pending ___ Python tracker _

[issue6389] os.chmod() documentation refers to non-existent documentation in stat

Georg Brandl added the comment: I agree with David. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue6384] Permalink to built-in exception class hierarchy documentation

Georg Brandl added the comment: I added a new heading there in r73706. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue6389] os.chmod() documentation refers to non-existent documentation in stat

R. David Murray added the comment: Since the constants are listed in the os.chmod section of the manual, do I understand that you are suggesting that the eplanations of the meanings of the flags from the chmod man page be added to that list? I observe that in the unix man pages the flags are do

[issue6374] Confused by subprocess API documentation

Georg Brandl added the comment: Thanks, committed in r73705. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ ___

[issue6376] description of Decinal.logical_invert is incorrect

Georg Brandl added the comment: Fixed in r73704. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue6389] os.chmod() documentation refers to non-existent documentation in stat

New submission from Michael : If you look at the documentation for os.chmod(), it says: "mode may take one of the following values (as defined in the stat module)..." and then lists a number of constants from the stat module (stat.S_ISUID, stat.S_ISGID, etc.) I cannot seem to find these constan

[issue6347] hpux11.00-parisc: dtoa.c: "Failed to find an exact-width 32-bit integer type"

Mark Dickinson added the comment: Thanks. That all seems fairly clear cut: HP-UX defines everything integer-related that C99 expects it to, but puts it in inttypes.h rather than stdint.h. Given that the autoconf tests for uint32_t and friends are checking both stdint.h and inttypes.h, and

[issue6367] Change the instruction pointer in python

vinoth <4vin...@gmail.com> added the comment: HI Exceptions are doing exactly the right way. but what I am telling is a new way of flow control which no languages currently having. On Tue, Jun 30, 2009 at 12:14 PM, Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > > So there

[issue6363] __future__ statements break doctest

Poor Yorick added the comment: here is a monkey patch to work around the problem: import __future__ import doctest if sys.version_info.major > 2: _extract_future_flags_old = doctest._extract_future_flags def _extract_future_flags(globs): flags = _extract_future_f

[issue1293741] doctest runner cannot handle non-ascii characters

Christoph Burgmer added the comment: See attached patch which works for error reporting and verbose output. -- keywords: +patch nosy: +christoph Added file: http://bugs.python.org/file14407/doctest.unicode.patch ___ Python tracker

[issue3955] maybe doctest doesn't understand unicode_literals?

Christoph Burgmer added the comment: This problem seems more severe as the appended test case shows. That gives me: Expected: u'ī' Got: u'\u012b' Both literals are the same. Unicode literals in doc strings are not treated as other escaped characters: >>> repr(r'\n') "'n'" >>> r

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: Right. Actually unicodetype_db.h is the one included in unicodectype.c, I moved my script into makeunicodedata.py. Here is a new patch. The code generated for _PyUnicode_ToNumeric is the same as before (except for some tabs), see the old patch if you want

[issue6387] floor division gives different result for int versus float.

Changes by R. David Murray : -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue6363] __future__ statements break doctest

Poor Yorick added the comment: It seems that "compile" does not recognize some flags: Python 3.1 (r31:73574, Jun 26 2009, 20:21:35) [MSC v.1500 32 bit (Intel)] on win 32 Type "help", "copyright", "credits" or "license" for more information. >>> import __future__ >>> compile('a=5', '', 'single',

[issue6387] floor division gives different result for int versus float.

Tim Peters added the comment: Yup, -1 here too. For dyadic arithmetic operations (+ - * / % //) on mixed numeric types, Python's execution model coerces the operands to a common type before computation begins. Besides just being the way it's worked "forever" in Python, it's consistent and expl

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Yitz Gale : -- nosy: +ygale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/ma

[issue6387] floor division gives different result for int versus float.

Eric Smith added the comment: I agree with Mark: -1. Do you have any specific use cases where this has caused problems, or is this academic? Maybe you can get some support for this on python-ideas, but I suggest we close it in the meantime. -- ___

[issue6387] floor division gives different result for int versus float.

Mark Dickinson added the comment: This is definitely a feature request rather than a bug. As I understand it, you want to special-case floor division so that if the argument types are (int, float) or (float, int) then the result is computed exactly. Is that correct? Note that the result of t

[issue6369] binhex buggy in py3k

Antoine Pitrou added the comment: Well, failure or success of the current tests seems to rely on the length of the filename being tested! :-) -- ___ Python tracker ___ __

[issue6387] floor division gives different result for int versus float.

Changes by R. David Murray : -- nosy: +eric.smith, marketdickinson priority: -> low ___ Python tracker ___ ___ Python-bugs-list mailin

[issue6388] platform.python_implementation does not work on IronPython

Benjamin Peterson added the comment: It should in 2.7, when that is released. -- nosy: +benjamin.peterson resolution: -> out of date status: open -> closed ___ Python tracker __

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Benjamin Peterson added the comment: Wouldn't it make more sense to move this into unicode_db.h? -- nosy: +benjamin.peterson, loewis ___ Python tracker ___ __

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

Changes by Jesse Noller : Removed file: http://bugs.python.org/file14320/0001-Fix-issue-5313.patch ___ Python tracker ___ ___ Python-bugs-list

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

Changes by Jesse Noller : Removed file: http://bugs.python.org/file14319/stdin-patchv1.patch ___ Python tracker ___ ___ Python-bugs-list mailin

[issue6387] floor division gives different result for int versus float.

David Jones added the comment: I do realise that. I still think the mathematically correct answer should be computed, since it can be. -- ___ Python tracker ___ ___

[issue6388] platform.python_implementation does not work on IronPython

New submission from Thomas Bleier : platform.python_implementation as of CPython 2.6 does not work on IronPython 2.0.1 It obviously crashes because it fails determining that it run's on IronPython. >>> platform.python_implementation() Traceback (most recent call last): File "", line 1, in

[issue6387] floor division gives different result for int versus float.

Tim Peters added the comment: Do you realize that 2**54-1 isn't exactly representable as a float? It requires 54 bits of precision, but the Python float format only has 53 bits available (on all popular boxes). >>> 2**54-1 18014398509481983L >>> float(_) # rounds to closest representable floa

[issue6387] floor division gives different result for int versus float.

New submission from David Jones : Consider: x//y != x//float(y) for some integer values of x and y. For example, x = 2**54-1, and y = 2: >>> x=2**54-1 >>> y=2 >>> x//y 9007199254740991L >>> x//float(y) 9007199254740992.0 >>> _==x//y False I have no idea whether this should actually be a bug or

[issue6386] importing yields unexpected results when initial script is a symbolic link

Changes by jan matejek : -- nosy: +matejcik ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue6386] importing yields unexpected results when initial script is a symbolic link

New submission from jbeulich : Due to the way PySys_SetArgv() works, when the initial script is a symbolic link, importing from normal files in the same directory does not work. This is particularly surprising when the work tree is a symlinked clone (cp -s) of an original (i.e. snapshot) tree wit

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: The _PyUnicode_ToNumeric() function was not in line with the unicode database. Here is a new version of this function, together with the script to generate its code. -- keywords: +needs review, patch nosy: +amaury.forgeotdarc Added file: http://bu

[issue6385] two lines of typographical inconsistency in doc of exception class hierarchy

Georg Brandl added the comment: Fixed in Pygments trunk. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py