[issue4322] function with modified __name__ uses original name when there's an arg error

New submission from Erick Tryzelaar <[EMAIL PROTECTED]>: I ran into a case where I modified the __name__ attribute of a function and then didn't specify the right number of arguments, and I got a TypeError that used the original function name, as demonstrated here: >>> def foo(): pass ... >>>

[issue4321] unintended syntax error with decorators, parenthesis, and dots?

David W. Lambert <[EMAIL PROTECTED]> added the comment: Guido gets to choose. Read PEP:318 Title: Decorators for Functions and Methods and "gut feeling" http://mail.python.org/pipermail/python-dev/2004-August/046711.html -- nosy: +LambertDW _

[issue4191] urlparse normalize URL path

Senthil <[EMAIL PROTECTED]> added the comment: This report almost seems like a bug with urlparse, but it is not. We have to consider certain cases here. 1) First of all, we cannot equate urlparsing, urlsplit, urljoin with path normalization provided by posixpath.normalize. The reason is the url

[issue4321] unintended syntax error with decorators, parenthesis, and dots?

New submission from Erick Tryzelaar <[EMAIL PROTECTED]>: I believe I found an unintentional syntax error with a combination of decorators, parenthesis, and dots. Here's a demonstration: class C: def prop(self, function): return property(function) class F: @C().prop def foo(

[issue4111] Add DTrace probes

Laszlo (Laca) Peter <[EMAIL PROTECTED]> added the comment: I'm the python package maintainer at Sun. We would really like to get the dtrace probes upstream, let me know how I can help. -- nosy: +laca ___ Python tracker <[EMAIL PROTECTED]>

[issue4320] optparse: "1 2 3" should be seen as one string

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: (copied from the Optik bug tracker -- I haven't tried to replicate this.) -- components: Library (Lib) messages: 75848 nosy: akuchling severity: normal status: open title: optparse: "1 2 3" should be seen as one string versions: Pyth

[issue4319] optparse and non-ascii help strings

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: (copied from the Optik bug tracker) Related bug: http://www.mail-archive.com/python-bugs-list@python.org/msg07227.html Hi all, It seems to me that the workaround to the above bug in optparse.py versio 1.5.3 introduces a new bug when help s

[issue4318] optparse: formatting of help text/descriptions

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: (Copied from an anonymous submission in the Optik bug tracker.) There have been some recent discussions on comp.lang.python about the optparse/optik module, and Steve Bethard suggested you might be interested in some of the work done there.

[issue1665333] Documentation missing for OptionGroup class in optparse

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: Re-opening, since Optik is no longer externally maintained. -- assignee: -> akuchling nosy: +akuchling resolution: invalid -> status: closed -> open title: Documentation missing for OptionGroup class in optparse -> Documentation mi

[issue1699259] replacing char* with const char* in sysmodule.c/.h

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: While technically this is an API change, in reality it is unlikely to break anyone's code because you can always pass char * to a function that expects const char* and the ABI does not change. (Also I cannot think why anyone would want

[issue2869] Wrong doc for `calendar.Calendar.iterweekdays`

benny daon <[EMAIL PROTECTED]> added the comment: It confused me. Got to this URL: http://www.python.org/doc/2.5.2/lib/module-calendar.html -- nosy: +daonb ___ Python tracker <[EMAIL PROTECTED]> _

[issue4317] Buffer overflow in imageop module

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Of course I uploaded the wrong patch. Trying again. Added file: http://bugs.python.org/file12002/rgbcrash.diff ___ Python tracker <[EMAIL PROTECTED]> __

[issue4317] Buffer overflow in imageop module

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file12001/rgbcrash.diff ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4317] Buffer overflow in imageop module

STINNER Victor <[EMAIL PROTECTED]> added the comment: Ooops. That's why I asked for one or more reviewers :-) -- nosy: +haypo ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4317] Buffer overflow in imageop module

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: The interpreter sometimes segfaults when running the test suite, in test_imageop. A more reliable crasher is: >>> import imageop >>> s = "A" * 32000 >>> imageop.rgb2rgb8(s, 1, len(s)) The failure was recently introduced by r66689, a

[issue1699259] replacing char* with const char* in sysmodule.c/.h

Christian Heimes <[EMAIL PROTECTED]> added the comment: Sorry, but it's too late to apply the patch. The issues don't count as "critical" and it changes the API, too. Only critical and important bugs are solved during the release candidate phase of 3.0. Python 2.6 is already out. I set the targe

[issue1814] Victor Stinner's GMP patch for longs

STINNER Victor <[EMAIL PROTECTED]> added the comment: Notes: - GNU Common LISP uses CLN, which uses GMP's low-level functions (http://cvs.savannah.gnu.org/viewvc/gcl/gcl/gmp/) - GHC (Haskell compiler, http://haskell.org/ghc/) uses (or used) GMP. But Haskell is a statically typed language, where

[issue1699259] replacing char* with const char* in sysmodule.c/.h

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- nosy: +jhylton ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue1699259] replacing char* with const char* in sysmodule.c/.h

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: The new patch looks fine to me. It applies and compiles without warnings and the changes are now reflected in the docs. I guess someone would need to write a NEWS entry because it is a public API change, but otherwise I would say it s

[issue1716] String format operator '%i' fails for large floats

Mark Dickinson <[EMAIL PROTECTED]> added the comment: > I think in 2.6 we can't change this, I'm not sure when it happened, but it looks like this *was* fixed for 2.6. Closing. -- nosy: +marketdickinson resolution: -> fixed status: open -> closed _

[issue4316] Improper use of [] in configure.in leads to useless regexp in configure

New submission from Soren jacobsen <[EMAIL PROTECTED]>: "NetBSD/1.6[A-S]" is what is desired in configure, but the wrong configure.in goop is used, so "NetBSD/1.6A-S" is generated instead. Apply the attached patch, commit configure.in, run autoreconf, commit configure. -- components:

[issue4111] Add DTrace probes

Ted Leung <[EMAIL PROTECTED]> added the comment: And courtesy of Philip Jenvey, here I am. I would *really* like to work to help make this happen. Laszlo Peter at Sun has been doing the ports of Python on Solaris, but we are not up to 2.6 just yet. I'm attaching a pointer to his patches again

[issue1699259] replacing char* with const char* in sysmodule.c/.h

Sebastian Ramacher <[EMAIL PROTECTED]> added the comment: At least a response, finally. > * Any reason why PySys_SetPath(char *) is left out? I guess it I just missed it. > * Same for PySys_SetArgv(int, char **) That one is non-trivial and requires some rewriting of PySys_SetArgv. And I did

[issue4111] Add DTrace probes

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Thu, Nov 13, 2008 at 08:05, Skip Montanaro <[EMAIL PROTECTED]> wrote: > > Skip Montanaro <[EMAIL PROTECTED]> added the comment: > > Brett> http://www.opensource.apple.com/darwinsource/10.5.5/python-30.1.2/ >... >Brett> > http://cvs.o

[issue4315] On some Python builds, exec in a function can't create shadows of variables if these are declared "global" in another function of the same module

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-

[issue2996] IDLE "find in files" output not formatted optimally

Changes by Russell Blau <[EMAIL PROTECTED]>: -- versions: +Python 2.5.3, Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pytho

[issue4315] On some Python builds, exec in a function can't create shadows of variables if these are declared "global" in another function of the same module

Silas S. Brown <[EMAIL PROTECTED]> added the comment: Sorry, I accidentally posted the workaround code instead of the bug example. This is what I should have posted: setting1 = "val1" setting2 = "val2" def dummy(): global setting1 def f(x): exec(x) return setting1,setting2 print

[issue4295] closing stdout in a child process on cygwin means that process doesn't receive bytes from stdin anymore. I think.

Zooko O'Whielacronx <[EMAIL PROTECTED]> added the comment: Corinna Vinschen of cygwin requests a smaller test case: http://www.cygwin.com/ml/cygwin/2008-11/msg00166.html ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4315] On some Python builds, exec in a function can't create shadows of variables if these are declared "global" in another function of the same module

New submission from Silas S. Brown <[EMAIL PROTECTED]>: Here's the example code: setting1 = "val1" setting2 = "val2" def dummy(): global setting1 def f(x): d ={"setting1":setting1,"setting2":setting2} exec(x) in d return d['setting1'], d['setting2'] print f("setting1=setting2=

[issue4111] Add DTrace probes

Skip Montanaro <[EMAIL PROTECTED]> added the comment: Brett> http://www.opensource.apple.com/darwinsource/10.5.5/python-30.1.2/ ... Brett> http://cvs.opensolaris.org/source/xref//jds/spec-files/trunk/patches/Python-07-dtrace.diff Thanks for the pointers. I'll work on getting a uniform

[issue4314] isalpha bug

STINNER Victor <[EMAIL PROTECTED]> added the comment: $ python Python 2.5.1 (r251:54863, Jul 31 2008, 23:17:40) >>> print u'\u0451' ё >>> print u'\u0427' Ч @ZooKeeper: Try Python 2.6, I guess that your bug is already fixed. ___ Python tracker <[EMAIL PROTECTE

[issue4314] isalpha bug

ZooKeeper <[EMAIL PROTECTED]> added the comment: I'll investigate it in further shortly, but for now replicating the test. print u'\u0451' ¸ print u'\u0427' × Something must be going on here. Running Win XP. ___ Python tracker <[EMAIL PROTECTED]>

[issue4111] Add DTrace probes

Brett Hoerner <[EMAIL PROTECTED]> added the comment: On Wed, Nov 12, 2008 at 9:31 PM, Skip Montanaro <[EMAIL PROTECTED]> wrote: > I see the reference to Apple in your original post, but can't find anything > related to dtrace & python starting from the URL you gave. Do you have > something more

[issue4314] isalpha bug

STINNER Victor <[EMAIL PROTECTED]> added the comment: Results on Linux: With Python 2.7 trunk: >>> print(', '.join('%s:%s' % (c, c.isalpha()) for c in u'абвгдеч')) а:True, б:True, в:True, г:True, д:True, е:True, ч:True With Python 2.5.1: >>> print(', '.join('%s:%s' % (c, c.isalpha()) for c in u

[issue4314] isalpha bug

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: ... and for the other character: >>> print u'\u0427' Ч >>> print u'\u0447' ч >>> print u'\u0427'.isalpha() True >>> print u'\u0447'.isalpha() True Looks fine. -- resolution: -> works for me status: open -> closed _

[issue4314] isalpha bug

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: FWIW: I get the following in Python 2.5: >>> print u'\u0401' Ё >>> print u'\u0451' ё >>> print u'\u0401'.isalpha() True >>> print u'\u0451'.isalpha() True ___ Python tracker <[EMAIL PROTECTED]>

[issue4314] isalpha bug

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: Are you sure that you've used the right source code encoding for writing these characters ? Note that the Unicode .isalpha() method relies entirely on what the Unicode database provides as code point information. If a character is marked

[issue4314] isalpha bug

New submission from ZooKeeper <[EMAIL PROTECTED]>: This may be a little tricky to recreate but here it is: q = u'абвгде' q.isalpha() True foo = u'ч' foo.isalpha() False So the Russian character u'ч' and u'ё' as well as a bunch of others is not recognized by isalpha as a alphabetic character, w

[issue4295] closing stdout in a child process on cygwin means that process doesn't receive bytes from stdin anymore. I think.

Changes by Jean-Paul Calderone <[EMAIL PROTECTED]>: -- nosy: +exarkun ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue4313] IDLE segfault at exit

STINNER Victor <[EMAIL PROTECTED]> added the comment: The bug looks to be specific to Python3 but may comes from Tk and not directly from tkinter module. I recompiled Tk with debug symbols to get a better backtrace: malformed bucket chain in Tcl_DeleteHashEntry Program received signal SIGABRT,

[issue1222] locale.format bug if thousand separator is space (french separator as example)

Changes by Walter Doekes <[EMAIL PROTECTED]>: -- nosy: +wdoekes ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue4313] IDLE segfault at exit

STINNER Victor <[EMAIL PROTECTED]> added the comment: The crash occurs when I close a window if a file was open. I can reproduce the crash on Debian Sid, so it's not a problem of an old library version. ___ Python tracker <[EMAIL PROTECTED]>

[issue4313] IDLE segfault at exit

New submission from STINNER Victor <[EMAIL PROTECTED]>: With Python 3.0 trunk on Ubuntu Gutsy, IDLE crashs at exit. gdb trace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210763072 (LWP 9441)] 0xb79ac133 in Tk_Free3DBorder () from /usr/lib/libtk8.4.so.0 (gdb) wher

[issue4312] Unicode in distutils meta-data?

New submission from Hagen Fürstenau <[EMAIL PROTECTED]>: http://docs.python.org/dev/3.0/distutils/setupscript.html#additional-meta-data says "None of the string values may be Unicode.". How is this to be interpreted (or changed) w.r.t. Python 3.0? -- assignee: georg.brandl components: D

[issue887237] Machine integers

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Is it be feasible to add arithmetic operations to the ctypes integer types? Since ctypes is now in the core, it would seem better to enhance ctypes than provide a new module. I think this would be valuable for rapid prototyping of an algorit