[issue1575] typo in README

New submission from Andrew Dalke: Current text in README: See Mac/OSX/README for more information on framework and universal builds. Should be See Mac/README for more information on framework and universal builds. because r46719 moved Mac/OSX/* one level up (

[issue1574] Touchpad 2 Finger scroll does not work in IDLE on Mac (But scroll wheel of external mouse does)

Changes by Puneet Arora: -- components: IDLE nosy: arorap severity: normal status: open title: Touchpad 2 Finger scroll does not work in IDLE on Mac (But scroll wheel of external mouse does) type: behavior versions: Python 2.5 __ Tracker <[EMAIL PROTECTE

[issue1572] 404 report of SimpleXMLRPCServer is broken

Christian Heimes added the comment: No, I've fixed the three failing or blocking tests in r59429 and r59434. __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue1572] 404 report of SimpleXMLRPCServer is broken

Guido van Rossum added the comment: Is disabling a test the right solution? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu

[issue1550] help('modules') broken by several 3rd party libraries (svn patch attached)

Changes by Christian Heimes: -- assignee: -> ping keywords: +patch nosy: +ping priority: -> normal versions: +Python 3.0 __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1572] 404 report of SimpleXMLRPCServer is broken

Changes by Christian Heimes: -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1564] The set implementation should special-case PyUnicode instead of PyString

Christian Heimes added the comment: I've created a patch that adds optimization for PyUnicode while keeping the existing optimization for PyString. The patch moves the optimization trick for PyObject_Hash() into a macro and adds an optimized _PyUnicode_Eq() to unicodeobject.c -- assignee

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Amaury Forgeot d'Arc added the comment: Right. We should also replace the other occurence of "no name for vararg". Here is another patch, against the current revision (59434). Added file: http://bugs.python.org/file8895/kwonly2.patch __ Tracker <[EMAIL PROTECTED]

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Christian Heimes added the comment: Here is another error message from Thomas Wouters 'named arguments must follow bare *' __ Tracker <[EMAIL PROTECTED]> __

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Christian Heimes added the comment: Kirk McDonald has an even better error message for us: SyntaxError: Cannot specify keyword only arguments without named arguments __ Tracker <[EMAIL PROTECTED]> ___

[issue1564547] Py_signal_pipe

Guido van Rossum added the comment: I've been told to look at this one more time. -- assignee: -> gvanrossum nosy: +gvanrossum resolution: rejected -> status: closed -> open _ Tracker <[EMAIL PROTECTED]> ___

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Christian Heimes added the comment: Ah, you and Amaury are right! But I don't like Amaury's error message: SyntaxError: no name for vararg It doesn't explain what's wrong. How about SyntaxError: keyword only arguments require at least one keyword __ Tra

[issue914148] xml.sax segfault on error

Facundo Batista added the comment: 2007/12/8, Adam Sampson <[EMAIL PROTECTED]>: > On Fri, Dec 07, 2007 at 08:07:38PM -, Facundo Batista wrote: > > There's no crash in 2.5.1 neither in the trunk. > > As 2.3 or 2.4 won't be fixed, do you think that this bug can be closed? > > Yep, go for it.

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Amaury Forgeot d'Arc added the comment: > Why do you want to forbid > def f(*, **kw) Well, TOOWTDI and the like... and the first time I saw it, it seemed that any number of parameters is allowed! __ Tracker <[EMAIL PROTECTED]>

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Alexandre Vassalotti added the comment: Amaury is right. "def f(*, **kw): pass" should raise a SyntaxError. The keyword-only delimiter is useless since the **kw parameter already only accepts keywords. __ Tracker <[EMAIL PROTECTED]>

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Christian Heimes added the comment: Why do you want to forbid def f(*, **kw) ? It's useful and it also works in release builds of Python 3.0a2. It only breaks in debug builds because the assert() gets triggered. __ Tracker <[EMAIL PROTECTED]>

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Changes by Amaury Forgeot d'Arc: -- status: closed -> open __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Amaury Forgeot d'Arc added the comment: Err... I think it should raise a SyntaxError in this case. See my attached patch. -- nosy: +amaury.forgeotdarc Added file: http://bugs.python.org/file8894/kwonly.patch __ Tracker <[EMAIL PROTECTED]>

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Changes by Christian Heimes: -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Christian Heimes added the comment: Fixed in r59432 I've altered the assert(). It now checks if either kwonlyargs and kwdefault or both not NULL or the next node is a DOUBLESTAR. -- nosy: +tiran __ Tracker <[EMAIL PROTECTED]>

[issue1573] Improper use of the keyword-only syntax makes the parser crash

Changes by Alexandre Vassalotti: -- versions: +Python 3.0 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue1573] Improper use of the keyword-only syntax makes the parser crash

New submission from Alexandre Vassalotti: I found that the parser fails to handle correctly the (incorrect) case where the single-star (*), used for delimiting keyword-only arguments, is immediately followed by a **keywords parameter: >>> def f(*, **kw): ... pass ... python: Python/ast.c:652:

[issue1266570] PEP 349: allow str() to return unicode

Neil Schemenauer added the comment: On Sat, Dec 08, 2007 at 05:14:45AM -, Alexandre Vassalotti wrote: > The PEP has been deferred and the patch is out of date. So, is this > change still wanted? I still think it would make things easier for people using Unicode with Python 2.x. However, th

[issue1572] 404 report of SimpleXMLRPCServer is broken

Christian Heimes added the comment: I disabled test_404 in test_xmlrpc.py r59423 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Uns

[issue1572] 404 report of SimpleXMLRPCServer is broken

New submission from Christian Heimes: Exception happened during processing of request from ('127.0.0.1', 55017) Traceback (most recent call last): File "/home/heimes/dev/python/py3k/Lib/SocketServer.py", line 222, in handle_request self.process_request(request, client_address) File "/home

[issue1538] Avoid string copy when split char doesn't match

Skip Montanaro added the comment: In the absence of any more feedback, I checked this in as r59420. -- resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1510] help for file/open should state which is prefered.

Skip Montanaro added the comment: updated docstrings for file and open (r59417). -- nosy: +skip.montanaro resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1571] Better description of 'L' repr removal in "What's New"

Changes by Christian Heimes: -- assignee: -> georg.brandl keywords: +py3k nosy: +georg.brandl priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ __

[issue1571] Better description of 'L' repr removal in "What's New"

New submission from Ori Avtalion: The "common stumbling blocks" section reads: * Code that unconditionally strips the trailing ``L`` from the ``repr()`` of a long integer will chop off the last digit instead. This explains a problem and a fix without any reason (one has to guess it from contex