[issue2686] Any chance we could double the height of the 'Comment:' text area on tracker?

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- resolution: invalid -> fixed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing l

[issue2686] Any chance we could double the height of the 'Comment:' text area on tracker?

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Fixed in r62496. Amaury was right - please do use the meta-tracker in the future for this. But what should I do with your left arm now :-? FWIW, Safari users don't need to rely on the HTML page providing them with enough space - they can in

[issue2686] Any chance we could double the height of the 'Comment:' text area on tracker?

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10099/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10096/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10097/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10101/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10093/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10100/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10098/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10090/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10095/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10094/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10092/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10091/unnamed _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho

[issue1376292] Write user's version of the reference guide

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- title: Write user's version of -> Write user's version of the reference guide _ Tracker <[EMAIL PROTECTED]> _ ___

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1376292] Write user's version of

Changes by Georg Brandl <[EMAIL PROTECTED]>: _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1883] Adapt pydoc to new doc system

Humberto Diogenes <[EMAIL PROTECTED]> added the comment: Amaury, seems that there's duplicated from render_doc inside pydoc.doc. I removed it and everything kept working, including the new basic tests. Added file: http://bugs.python.org/file10103/py3k-pydoc.doc-cleanup.patch __

[issue1496032] test_float segfaults with SIGFPE on FreeBSD 6.0 / Alpha

Neal Norwitz <[EMAIL PROTECTED]> added the comment: I think `uname -m` will be equal to "alpha" in this case. There are several uses of `uname -m` in configure.in. You might need to add a new section. It might also be possible to clean up various special cases to make a generic `uname -m` sect

[issue2687] SSL example script fails mysteriously on MacOS

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: On my MacOS 10.4.11 machine, the example SSL server and client in the documentation don't work, and they fail with a mysterious error 0. The attached tarball contains my slightly-modified version of the scripts and the test key/cert I'm usin

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. Added file

[issue1376292] Write user's version of

bob gailer <[EMAIL PROTECTED]> added the comment: My new email address is bgailer at gmail dot com (not google dot com). Please update your address book, and change the above into the form [EMAIL PROTECTED] The old address will expire at the end of 2008. Bob Gailer in Chapel Hill NC. --

[issue1376292] Write user's version of RefGuide

bob gailer <[EMAIL PROTECTED]> added the comment: I find a Reference Manual and a Library Reference. I presume you are referring to the Reference Manual. True? I might be interested in helping create the shorter friendlier guide. I suggest we create some guidelines or specifications for it. This

[issue2632] performance problem in socket._fileobject.read

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: available for an easy side by side review here: http://codereview.appspot.com/212 Also, yes I think you're right Ralf. With these changes I should be able to return that to a max() within the while True: for sized reads and things will w

[issue2686] Any chance we could double the height of the 'Comment:' text area on tracker?

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: +1 But you should file this in the Meta-Tracker; click "Report Tracker Problem" at the bottom of the left bar. -- nosy: +amaury.forgeotdarc __ Tracker <[EMAIL PROTECTED]>

[issue2686] Any chance we could double the height of the 'Comment:' text area on tracker?

New submission from Trent Nelson <[EMAIL PROTECTED]>: I'd give my left arm for the comment box to be at least double its current height. Once you've written more than a paragraph, it becomes a nuisance having to scroll up and down to re-read what you've written before typing more. Quick win? -

[issue2672] speed of set.update(

John Arbash Meinel <[EMAIL PROTECTED]> added the comment: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Raymond Hettinger wrote: > Raymond Hettinger <[EMAIL PROTECTED]> added the comment: > > John, when y=[], the update method has to create a new list iterator on > each invocation. But when y

[issue2672] speed of set.update(

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: John, when y=[], the update method has to create a new list iterator on each invocation. But when y is a genexp, it is self-iterable (iow, iter (y) will return self, not a new object). Also, when doing timings, it can be helpful to facto

[issue2685] Add -mieee to compile flags, when available

Mark Dickinson <[EMAIL PROTECTED]> added the comment: See also issue 1496032. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubsc

[issue433024] SRE: (?flag) isn't properly scoped

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc Tracker <[EMAIL PROTECTED]> ___ Python-bugs-list mailing list Unsubscribe: h

[issue1721518] Small case which hangs

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue2685] Add -mieee to compile flags, when available

New submission from Mark Dickinson <[EMAIL PROTECTED]>: test_math and test_cmath currently fail on Debian/alpha, apparently due to mishandling of subnormal numbers. I have high hopes that this can be fixed by compiling with -mieee. The attached patch modifies the configure script to always us

[issue1297193] Search is to long with regex like ^(.+|dontmatch)*$

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1647489] zero-length match confuses re.finditer()

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1883] Adapt pydoc to new doc system

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Humberto, I added your test file in trunk. I added some other tests: now pydocfodder.py is used by a basic "smoke test". The tests revealed two bugs in python3.0... Thanks! __ Tracker <[EMAIL PROTECTED]>

[issue1693050] \w not helpful for non-Roman scripts

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue433030] SRE: Atomic Grouping (?>...) is not supported

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc Tracker <[EMAIL PROTECTED]> ___ Python-bugs-list mailing list Unsubscribe: h

[issue1662581] the re module can perform poorly: O(2**n) versus O(n**2)

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1160] Medium size regexp crashes python

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue2537] re.compile(r'((x|y+)*)*') should fail

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue2636] Regexp 2.6 (modifications to current re 2.2.2)

Changes by Russ Cox <[EMAIL PROTECTED]>: -- nosy: +rsc __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue799428] tk_focusNext() fails

Guilherme Polo <[EMAIL PROTECTED]> added the comment: Sorry for the previous patch, correct one attached now Added file: http://bugs.python.org/file10088/bugfix_and_revamp_nametowidget.diff Tracker <[EMAIL PROTECTED]> ___

[issue799428] tk_focusNext() fails

Changes by Guilherme Polo <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10087/bugfix_and_revamp_nametowidget.diff Tracker <[EMAIL PROTECTED]> _

[issue799428] tk_focusNext() fails

Guilherme Polo <[EMAIL PROTECTED]> added the comment: There was a problem with my previous patch if the widget name was just '.' New patch attached Added file: http://bugs.python.org/file10087/bugfix_and_revamp_nametowidget.diff Tracker <[EMAIL PROTECTED]> <

[issue799428] tk_focusNext() fails

Changes by Guilherme Polo <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9938/bugfix_and_revamp_nametowidget.diff Tracker <[EMAIL PROTECTED]> __

[issue2471] imp.get_magic() should return bytes, not bytearray

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Oops, sorry for missing the tracker item. The change was sleeping in my workspace for some time... Thanks for closing it. -- nosy: +amaury.forgeotdarc __ Tracker <[EMAIL PROTECTED]>

[issue2471] imp.get_magic() should return bytes, not bytearray

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This was fixed as r62484. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2684] Logging Module still failing for %(filename)s, __init__

Charles Merriam <[EMAIL PROTECTED]> added the comment: oops, last line should be "exits the stack frames for the logging module. This should be a once-per-program-execution event" Hmm.. tracker should have a preview button. __ Tracker <[EMAIL PROTECTED]>

[issue2684] Logging Module still failing for %(filename)s, __init__

New submission from Charles Merriam <[EMAIL PROTECTED]>: About same as problem in 2.4 Issue1470422 closed without a test case on MacOS X/Python 2.4. Also same as http://mail.python.org/pipermail/python-bugs-list/2004-July/024111.html and so on back for years. What happens: [EMAIL PROTECTED]:~/p

[issue2683] subprocess.Popen.communicate takes bytes, not str

New submission from Lenard Lindstrom <[EMAIL PROTECTED]>: subprocess.Popen.communicate is documented as taking a string as the input argument. Instead is accepts only a binary stream (bytes). Python 3.0a4 (r30a4:62126, Apr 3 2008, 15:34:18) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "

[issue2672] speed of set.update(

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Thu, Apr 24, 2008 at 2:23 PM, John Arbash Meinel <[EMAIL PROTECTED]> wrote: .. > So if you compare consuming a generator multiple times to creating it > each time, it is 0.662 usec - 0.173 usec = 0.489 usec to create a generator. >

[issue2682] cyclic reference in ctypes CFunctionType objects

Thomas Heller <[EMAIL PROTECTED]> added the comment: Fixed in trunk and py3k, committed as rev 62481 (trunk), rev 62484 (py3k). I'll leave this open until the decision about backporting to release25-maint is made. -- resolution: -> accepted __ Tracker <

[issue2682] cyclic reference in ctypes CFunctionType objects

Thomas Heller <[EMAIL PROTECTED]> added the comment: > Can you please elaborate your (apparent) concerns about this patch? IOW, > why did you not check it in? I have no concerns about the patch, and I am currently committing it. I'm uploading so that I can points others to it, and (hopefully) to

[issue2680] gotcha: _fields_ is final but accepts lists

Thomas Heller <[EMAIL PROTECTED]> added the comment: Closing as won't fix. -- resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue2682] cyclic reference in ctypes CFunctionType objects

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Can you please elaborate your (apparent) concerns about this patch? IOW, why did you not check it in? -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> ___

[issue2682] cyclic reference in ctypes CFunctionType objects

New submission from Thomas Heller <[EMAIL PROTECTED]>: Zachary Pincus posted a message about this cyclic reference in ctypes CFunctionType objects. The reference has the problem that these objects are cleaned up later than expected. The attached patch fixes this problem by removing the cyclic r

[issue2636] Regexp 2.6 (modifications to current re 2.2.2)

Jim Jewett <[EMAIL PROTECTED]> added the comment: Python 2.6 isn't the last, but Guido has said that there won't be a 2.10. > Match object is a C-struct with python binding > and I'm not exactly sure how to add either feature to it I may be misunderstanding -- isn't this just a matter of writin

[issue2672] speed of set.update(

John Arbash Meinel <[EMAIL PROTECTED]> added the comment: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Belopolsky wrote: > Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: > > This has nothing to do with set.update, the difference is due to the > time to setup the generato

[issue2655] Create ctypes instances from buffer interface

Thomas Heller <[EMAIL PROTECTED]> added the comment: The suggestion by Lenard Lindstrom was an additional method named 'from_buffer_copy'. __ Tracker <[EMAIL PROTECTED]> __

[issue2680] gotcha: _fields_ is final but accepts lists

Thomas Heller <[EMAIL PROTECTED]> added the comment: > The __slots__ member of a class object has the same behavior. > You may mutate it (even replace it) but this has no effect: only the > value available when the "class" statement was executed is relevant. The rules in ctypes are a little bit

[issue2681] octal literals beginning with 8 don't raise a SyntaxError

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Corrected as r62480. I changed your patch a little bit: it seemed more logical to use (c < '0' || c >= '8') As it is the exact counterpart of ('0' <= c && c < '8') used a few lines below. Thanks for the report! -- nosy:

[issue2680] gotcha: _fields_ is final but accepts lists

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The __slots__ member of a class object has the same behavior. You may mutate it (even replace it) but this has no effect: only the value available when the "class" statement was executed is relevant. -- nosy: +amaury.forgeotdarc

[issue2681] octal literals beginning with 8 don't raise a SyntaxError

New submission from Lukas Meuser <[EMAIL PROTECTED]>: Octal literals containing an 8 or a 9 should raise a SyntaxError, but 8 ist accepted as the first character of such a literal (e.g., 0o8 or 0o876, but not 0o678). Those literals evaluate to 0.0. The fix for this is trivial, a patch against c

[issue2680] gotcha: _fields_ is final but accepts lists

New submission from Carlos Scheidegger <[EMAIL PROTECTED]>: When creating ctypes.Structure classes dynamically, there's a gotcha. _fields_ is final, but it takes a list that can be appended to. I'm not sure this is a bug, but I would argue it is a lot more surprising than it could be: Python 2.5

[issue2636] Regexp 2.6 (modifications to current re 2.2.2)

Jeffrey C. Jacobs <[EMAIL PROTECTED]> added the comment: Thanks Jim for your thoughts! Armaury has already explained about Perl 5.10.0. I suppose it's like Macintosh version numbering, since Mac Tiger went from version 10.4.9 to 10.4.10 and 10.4.11 a few years ago. Maybe we should call Python

[issue2636] Regexp 2.6 (modifications to current re 2.2.2)

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > > These features are to bring the Regexp code closer in line > > with Perl 5.10 > > Why 5.1 instead of 5.8 or at least 5.6? Is it just a scope-creep issue? 5.10.0 comes after 5.8 and is the latest version (2007/12/18)! Yes it is c

[issue2636] Regexp 2.6 (modifications to current re 2.2.2)

Jim Jewett <[EMAIL PROTECTED]> added the comment: > These features are to bring the Regexp code closer in line with Perl 5.10 Why 5.1 instead of 5.8 or at least 5.6? Is it just a scope-creep issue? > as well as add a few python-specific because this also adds to the scope. > 2) Make named m

[issue1496032] test_float segfaults with SIGFPE on FreeBSD 6.0 / Alpha

Mark Dickinson <[EMAIL PROTECTED]> added the comment: There are some current math and cmath test failures on the Debian alpha buildbots (2.6 and 3.0), and I think there's a good possibility that adding -mieee to BASECFLAGS would fix these. I'm struggling to find the right way to do this in con

[issue2679] email.feedparser regex duplicate

New submission from Jim Jewett <[EMAIL PROTECTED]>: feedparser defines four regexs for end-of-line, but two are redundant. NLCRE checks for the three common line endings. NLCRE_crack also captures the line ending. NLCRE_eol also adds a $ to ensure it is at the end. NLCRE_bol ... is identical to

[issue2678] hmac performance optimization

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: issue1618455 (r53065) already improved performance and was probably better: _strxor does not exist anymore, and has been replaced by a call to translate(). -- nosy: +amaury.forgeotdarc resolution: -> out of date status: open ->

[issue2650] re.escape should not escape underscore

Russ Cox <[EMAIL PROTECTED]> added the comment: > The loop in escape should really use enumerate > instead of "for i in range(len(pattern))". It needs i to edit s[i]. > Instead of using a loop, can't the test just > use "self.assertEqual(re.esacpe(same), same)?" Done. > Also, please add tes

[issue2678] hmac performance optimization

New submission from Nikolay Kim <[EMAIL PROTECTED]>: i removed lambda in _strxor function -- components: Library (Lib) files: hmac.py.diff keywords: patch messages: 65720 nosy: fafhrd severity: normal status: open title: hmac performance optimization type: performance versions: Python 2.

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Making it a documentation issue; I don't think the implementation should change. Georg, if you don't see the need for action, feel free to close it. -- assignee: -> georg.brandl components: +Documentation -Library (Lib) nosy: +georg

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi <[EMAIL PROTECTED]> added the comment: At present, "unspecified" is surely better than "you can't", that's a good point. I understand the difficulties of balancing the reference between the abstract definition and the actual implementation. But I still believe that this should

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Maybe yes, the easier but probably harmless solution is to change the > documentation and point out that "in general, you can't". Maybe this > somehow leans towards promoting a bug to the rank of feature? ;-) The language spec is stuck bet

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi <[EMAIL PROTECTED]> added the comment: > You are not completely wrong. It's just that this detail is something > most people recognize at some point and accept as a fact, regardless > of what the language specification says (and, as I claim, that text > isn't incorrect - or the

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > I'd believe you when you say "positional parameters are unnamed", but: > > - the language reference contains terms such as "first formal parameter > name". This means that positional parameters *may* have a name but may > also have no name

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi <[EMAIL PROTECTED]> added the comment: I'd believe you when you say "positional parameters are unnamed", but: - the language reference contains terms such as "first formal parameter name". This means that positional parameters *may* have a name but may also have no name? - if

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I fail to see the problem. The open function really doesn't have a named parameter called flags; the positional parameters are unnamed. So there is no violation of the language reference, AFAICT. Perhaps it would be useful to point out that s

  1   2   >