[issue1107] 2to3, lambda with non-tuple argument inside parenthesis

Georg Brandl added the comment: Assigned to Collin. -- assignee: -> collinwinter nosy: +collinwinter, georg.brandl title: [patch] 2to3, lambda with non-tuple argument inside parenthesis -> 2to3, lambda with non-tuple argument inside parenthesis __ Tra

[issue1105] patch for readme.txt in PCbuild8

Martin v. Löwis added the comment: Thanks for the patch. Committed as r57984 and r57985. -- nosy: +loewis resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue1106] Error in random.shuffle

Georg Brandl added the comment: Vizcaynot schrieb: > New submission from Vizcaynot: > > In python 3.0a1 under Win XP SP2: > Typing next code: > > import random > s=range(10) range() now returns an iterator, not a sequence, so random.shuffle() can't work on it. Use list(range()) if you want a l

[issue1092] Unexpected results in Tutorial about Unicode

Georg Brandl added the comment: OK, closing. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-l

[issue1107] [patch] 2to3, lambda with non-tuple argument inside parenthesis

Jeong-Min Lee added the comment: I found this while 2to3ing BeautifulSoup.py. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubs

[issue1107] [patch] 2to3, lambda with non-tuple argument inside parenthesis

New submission from Jeong-Min Lee: lambda (x): x should be transformed to lambda x: x not lambda x1: x1[0] -- components: Demos and Tools files: 2to3_lambda_nontuple_param.diff messages: 55654 nosy: falsetru, gvanrossum severity: normal status: open title: [patch] 2to3, lambda with n

[issue1106] Error in random.shuffle

New submission from Vizcaynot: In python 3.0a1 under Win XP SP2: Typing next code: import random s=range(10) random.shuffle(s) I have next error: Traceback (most recent call last): File "", line 1, in File "C:\python30\lib\random.py", line 262, in shuffle x[i], x[j] = x[j], x[i] TypeEr

[issue1583946] SSL "issuer" and "server" names cannot be parsed

Bill Janssen added the comment: I've changed the return value of ssl.sslsocket.getpeercert() to return the "issuer" and "subject" names as tuples containing 2-element name-value tuples, in the same order that they appear in the certificate. This should complete the fulfillment of this issue.

[issue1105] patch for readme.txt in PCbuild8

New submission from Ty: This update adds some comments to the readme.txt file for PCbuild8. When building subprojects VS2005 does not build the dependencies. I have included some text to alert the reader to this so they don't have the same trouble building subprojects as I did. I encountered t

[issue1092] Unexpected results in Tutorial about Unicode

Vizcaynot added the comment: Thanks about the fixing info. In relation to the second issue, I am afraid it is my fault, the value of variable "a" was asigned and filled with a previous valid operation. Please forgive me for the time you spent unnecessarily. I will attempt to be careful in the

[issue1104] msilib.SummaryInfo.GetProperty() truncates the string by one character

New submission from Anthony Tuininga : Attached is a patch that fixes the truncation of the property values returned by msilib.SummaryInfo.GetProperty(). Unfortunately Microsoft has deemed it necessary to return the size of

[issue1103] Typo in dummy_threading documentation

Dan Thomasset added the comment: Ahh, my mistake then. I misunderstood what was going on. Thanks, Dan On 9/4/07, Martin v. Löwis <[EMAIL PROTECTED]> wrote: > > > Martin v. Löwis added the comment: > > Why do you think so? The documentation is correct as it stands; > dummy_threading should be

[issue1102] Add support for _msi.Record.GetString() and _msi.Record.GetInteger()

Changes by Martin v. Löwis: -- assignee: -> loewis nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscri

[issue1103] Typo in dummy_threading documentation

Martin v. Löwis added the comment: Why do you think so? The documentation is correct as it stands; dummy_threading should be used when thread is not present, not when threading is not present (as threading will always be present, it just won't import when thread is not present). -- nosy:

[issue1101] Is there just no PRINT statement any more? Or it just doesn't work.

Martin v. Löwis added the comment: What's wrong with py> for x in 1,2,3:print(x,end=" ") ... 1 2 3 Closing as invalid. -- nosy: +loewis resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1103] Typo in dummy_threading documentation

New submission from Dan Thomasset: I believe that "thread" be "threading" in the line "...imported when the thread module is not provided..."? >From http://docs.python.org/lib/module-dummythreading.html -- components: Documentation messages: 55645 nosy: dthomasset severity: normal statu

[issue1102] Add support for _msi.Record.GetString() and _msi.Record.GetInteger()

Changes by Anthony Tuininga : -- type: behavior -> __ Tracker <[EMAIL PROTECTED]> __ _

[issue1102] Add support for _msi.Record.GetString() and _msi.Record.GetInteger()

New submission from Anthony Tuininga : Attached is a patch that adds the requested support. This is in relation to the thread at http://www.gossamer-threads.com/lists/python/python/584264 In addition to the two methods I a

[issue1102] Add support for _msi.Record.GetString() and _msi.Record.GetInteger()

Changes by Anthony Tuininga : -- components: Library (Lib) severity: normal status: open title: Add support for _msi.Record.GetString() and _msi.Record.GetInteger() type: behavior versions: Python 2.5 _

[issue1101] Is there just no PRINT statement any more? Or it just doesn't work.

New submission from Richard Katz: Is there supposed to be a way to do for x in 1,2,3: print x, If so, it's appears to be not working. Is it just not in this release? If not, I would think that leaving out the print statement (just because there is a print function) would represent a major

[issue1031213] Use correct encoding for printing SyntaxErrors

Guido van Rossum added the comment: We should make sure this is *not* merged into Py3k; there, things remain unicode until they're printed, at which point the only encoding that matters is the output file's encoding. _ Tracker <[EMAIL PROTECTED]>

[issue1031213] Use correct encoding for printing SyntaxErrors

Martin v. Löwis added the comment: Thanks for the patch. It wouldn't work as-is, because it broke PGEN. I fixed that, and committed the change as r57961 and r57962. -- resolution: -> accepted status: open -> closed versions: +Python 2.5, Python 2.6 _

[issue1374063] Broader iterable support for xmlrpclib

Skip Montanaro added the comment: Thanks for the feedback. I will reexamine what I've got. _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-li

[issue1388440] add more readline support

Changes by Martin v. Löwis: -- resolution: -> accepted status: open -> closed _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list m

[issue1388440] add more readline support

Martin v. Löwis added the comment: Thanks for the patch. Committed as r57960. -- nosy: +loewis versions: +Python 2.6 -Python 2.4 _ Tracker <[EMAIL PROTECTED]> _

[issue1376361] Use 'seealso' to add examples to LibRef

Martin v. Löwis added the comment: I'm closing this as out-of-date, now that the documentation format is not based on TeX anymore. If you would like to port this to Sphinx, feel free to reopen it (or submit any such feature as a new patch). -- nosy: +loewis resolution: -> out of date st

[issue1626801] posixmodule.c leaks crypto context on Windows

Martin v. Löwis added the comment: Ok, I added a comment in r57958 -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> _ __

[issue1374063] Broader iterable support for xmlrpclib

Martin v. Löwis added the comment: I have three problems with the current form of the patch: a) in the documentation, it should state that __dict__ is an attribute, not a method. b) why are you moving the subclassed-from-builtin types into the except block? It is there to reject things that have

[issue1100] Can't input non-ascii characters in interactive mode

Sangpil Yoon added the comment: It's working fine on Windows XP. Thanks. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe

[issue1092] Unexpected results in Tutorial about Unicode

Martin v. Löwis added the comment: The first issue (non-ASCII characters won't work in interactive mode) was reported as issue 1100 also, and is now fixed in r57957. As for the other issues, I'm not quite sure what to make out of them - I see a different behavior: py> "Äpfel".decode('latin-1).e

[issue1100] Can't input non-ascii characters in interactive mode

Martin v. Löwis added the comment: Thanks for the report. This is now fixed in r57957 (although I tested it only on Unix). -- nosy: +loewis resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]>