[issue1688] Incorrectly displayed non ascii characters in prompt using "input()" - Python 3.0a2

Guido van Rossum added the comment: I think I understand what's going on. The trail leads from the last "if (tty) {" block in builtin_input() to PyOS_Readline() which in turn ends up calling PyOS_StdioReadline() (because that's the most likely initialization of PyOS_ReadlineFunctionPointer). An

[issue1700463] VC6 build patch for trunk

Hirokazu Yamamoto added the comment: Umm, I found Py_intptr_t... OK, VC6 can compile HEAD. Please forget previous patch. I confirmed test_long.py, test_math.py, test_builtin.py successfully runs. Added file: http://bugs.python.org/file9046/vc6-trunk-ver4c.patch

[issue1700463] VC6 build patch for trunk

Hirokazu Yamamoto added the comment: Ummm, I realized my change is probably inproper... Index: Objects/intobject.c === --- Objects/intobject.c (revision 59671) +++ Objects/intobject.c (working copy) @@ -1053,7 +1053,7 @@ static

[issue1700463] VC6 build patch for trunk

Hirokazu Yamamoto added the comment: Sorry, I updated the patch again. - Add Python/pystrcmp.c to pythoncore.dsp. - Rev59671 contains intptr_t unavailable on VC6, avoid compile error by using PyLong_FromVoidPtr(). Added file: http://bugs.python.org/file9044/vc6-trunk-ver4.patch ___

[issue1720] VC6 build patch for release-maint25

Hirokazu Yamamoto added the comment: The patch for 2.6 is in issue1700463. I don't have a patch for 3.0 yet, but I'll try to make it. __ Tracker <[EMAIL PROTECTED]> __ _

[issue1725] -1e-1000 converted incorrectly

Mark Dickinson added the comment: Tracing the calls through ast_for_factor -> ast_for_atom -> parsenumber -> PyOS_ascii_atof -> PyOS_ascii_strtod -> strtod, it looks as though the cause is simply that strtod behaves differently on the two platforms. I get that the following code: #include

[issue1689] Backport PEP 3141 to 2.6

Jeffrey Yasskin added the comment: I've committed this as r59671, except that round() returns a float again to make sure we keep compatibility. Let me know if you find anything that needs fixing. __ Tracker <[EMAIL PROTECTED]> __

[issue1205] urllib fail to read URL contents, urllib2 crash Python

Guido van Rossum added the comment: I'm just following the last post's suggestion "Should we close this then?" My message (somebody "should" submit a patch) was sarcastic --- it was in reference to the comment that Python "should" be more practical. Since no patch was applied, I don't know why

[issue1205] urllib fail to read URL contents, urllib2 crash Python

Francesco Cosoleto added the comment: Sorry, but I don't understand reason to close this issue with resolution "wont fix". The problem was reproducible and his logic explained by more developers. If the problem has been resolved, then, please, change "resolution" field to "fixed", else a patch

[issue1567] Patch for new API method _PyImport_ImportModuleNoLock(char *name)

Guido van Rossum added the comment: Can you produce a version of the patch that applies cleanly to 2.6? Then we can apply it there first and merge into 3.0 later. But I wonder. It seems this changes every single call to PyImport_ImportModule() in the core to _PyImport_ImportModuleNoLock(). Wha

[issue1640] Enhancements for mathmodule

Guido van Rossum added the comment: One nit: you added a blank line to the end of test_math.py. This will cause the checkin to fail. :-) One bigger issue: the sign() function doesn't seem to work properly for nans. E.g. on Linux I get: >>> inf = 1e1000 >>> nan = inf/inf >>> mnan = -nan >>> mat

[issue1725] -1e-1000 converted incorrectly

Guido van Rossum added the comment: BTW this was on x86 Linux. On x86 OSX (10.4, Tiger) it works correctly: >>> -1e-1000 -0.0 __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1725] -1e-1000 converted incorrectly

New submission from Guido van Rossum: Since 1e-1000 == 0.0 (on an IEEE-754 platform anyway), I would expect -1e-1000 to be -0.0. But it does not appear that way: >>> 1e-1000 0.0 >>> -0.0 -0.0 >>> -1e-1000 0.0 However (correctly): >>> (-1.0) * 1e-1000 -0.0 >>> -(1e-1000) -0.0 I suspect the op

[issue1724] Py_SIZE() macro used as an lvalue

Martin v. Löwis added the comment: Certainly. This macro definitely *is* an lvalue. -- resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue1724] Py_SIZE() macro used as an lvalue

New submission from Raymond Hettinger: Don't know if this was intended. Here's a example from rev 56476 in arraymodule.c: - op->ob_size = size; + Py_Size(op) = size; -- assignee: loewis components: Interpreter Core messages: 59111 nosy: loewis, rhettinger severity: normal s

[issue1723] Respuesta automática de Yahoo!

Changes by Guido van Rossum: -- nosy: -gagenellina resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-

[issue1723] Respuesta automática de Yahoo!

New submission from Gabriel Genellina: Estoy de vacaciones hasta el 15 de enero! On holiday until Jan 15! -- messages: 59110 nosy: gagenellina severity: normal status: open title: Respuesta automática de Yahoo! __ Tracker <[EMAIL PROTECTED]>

[issue1205] urllib fail to read URL contents, urllib2 crash Python

Changes by Guido van Rossum: -- resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing l

[issue1698] urlparse and usernames containing @

Guido van Rossum added the comment: Could you please add a unit test for this? Then I can check it in. I'm thinking this could safely be fixed in 2.5.2. -- assignee: -> gvanrossum nosy: +gvanrossum resolution: -> accepted __ Tracker <[EMAIL PROTECTED]

[issue1692] Syntax Error exception dosen't print string; not informative

Guido van Rossum added the comment: Yup. Same if the exception comes in a file. I'll try to free up some cycles to look into this. Thanks for the report! -- assignee: -> gvanrossum nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]>

[issue1301] Bad assertion in _tkinter.c

Christian Heimes added the comment: I've hit the same bug today. I vote for the removal of the assert() and a skip of the entire block if size == 0. I don't see what the assert() should test. -- nosy: +tiran versions: +Python 2.6, Python 3.0 __ Tracker <[

[issue1708] improvements for linecache

Guido van Rossum added the comment: I'll look at this when I have time. If you find someone else interested in reviewing, please give them the patch! -- assignee: -> gvanrossum keywords: +patch nosy: +gvanrossum priority: -> low __ Tracker <[EMAIL PROTE

[issue1301] Bad assertion in _tkinter.c

Guido van Rossum added the comment: So what's the correct fix? Skip the whole block if size==0? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ _

[issue1721] _tkinter.c:903: AsObj: Assertion `size < size * sizeof(Tcl_UniChar)' failed

Martin v. Löwis added the comment: I think this is a duplicate of #1301 (reopen if you think it's not), where I think Facundo makes an excellent point. -- resolution: -> duplicate status: open -> closed superseder: -> Bad assertion in _tkinter.c __ Trac

[issue1696] Distutils ignore dry-run flag at clean-up of distutils.command.build_scripts.copy_scripts

Guido van Rossum added the comment: Committed revision 59668. (2.5 branch) Committed revision 59669. (2.6 trunk) -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue1722] Undocumented urllib functions

Changes by Guido van Rossum: -- assignee: -> georg.brandl nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing li

[issue1722] Undocumented urllib functions

New submission from Barry A. Warsaw: urllib.splithost() and .splittype() are included in urllib's __all__ but are not documented in urllib's module documentation. They are used quite extensively in the module so they should be documented __ Tracker <[EMAIL PROTEC

[issue1696] Distutils ignore dry-run flag at clean-up of distutils.command.build_scripts.copy_scripts

toxik added the comment: Mmh, well, as far as I could tell when I tested your patch, it didn't say it's going to copy the file, but it didn't say it isn't going to either. As far as this ticket is concerned however, I'd say the behavior is now fixed. __ Tracker <

[issue1722] Undocumented urllib functions

Changes by Barry A. Warsaw: -- components: Documentation nosy: barry priority: low severity: normal status: open title: Undocumented urllib functions versions: Python 2.5 __ Tracker <[EMAIL PROTECTED]> __

[issue1696] Distutils ignore dry-run flag at clean-up of distutils.command.build_scripts.copy_scripts

Guido van Rossum added the comment: So that's correct behavior right? (I looked at the code for copy_file() in cmd.py and it passes the dry_run parameter to the file utility function that does the actual copying. __ Tracker <[EMAIL PROTECTED]>

[issue1696] Distutils ignore dry-run flag at clean-up of distutils.command.build_scripts.copy_scripts

toxik added the comment: It shouldn't try to copy the script anywhere, it should just tell me what it was going to do, by means of console. __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1721] _tkinter.c:903: AsObj: Assertion `size < size * sizeof(Tcl_UniChar)' failed

Guido van Rossum added the comment: How about 2.6? -- assignee: -> loewis nosy: +gvanrossum, loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Pytho

[issue1696] Distutils ignore dry-run flag at clean-up of distutils.command.build_scripts.copy_scripts

Guido van Rossum added the comment: I'm not a big distutils expert myself, I can't quite interpret your feedback. In dry-run mode, it shouldn't try to copy the script, correct? -- keywords: +patch __ Tracker <[EMAIL PROTECTED]>

[issue1720] VC6 build patch for release-maint25

Christian Heimes added the comment: Do you have time to check and fix the VC6 build directories of Python 2.6 and 3.0, too? I don't think that they are up to date. -- assignee: -> loewis keywords: +patch nosy: +loewis, tiran priority: -> low __ Tracker

[issue1721] _tkinter.c:903: AsObj: Assertion `size < size * sizeof(Tcl_UniChar)' failed

New submission from Christian Heimes: $ ./python Lib/idlelib/idle.py python: /home/heimes/dev/python/py3k/Modules/_tkinter.c:903: AsObj: Assertion `size < size * sizeof(Tcl_UniChar)' failed. Aborted The code works when I change the assertion from "<" to "<=". My Python 3.0 is compiled with unico

[issue1720] VC6 build patch for release-maint25

New submission from Hirokazu Yamamoto: Hello. This patch adds missing _msi support. I confirmed msi file was successfully created for simple .py extension via "setup.py bdist_msi". Thank you. -- components: Build files: vc6-release-maint25.patch messages: 59094 nosy: ocean-city severity:

[issue1700463] VC6 build patch for trunk

Hirokazu Yamamoto added the comment: I updated the patch. - Added missing _msi support - Workaround for PC/msvcrtmodule.c (getwch not exists on VC6) Added file: http://bugs.python.org/file9042/vc6-trunk-ver3.patch _ Tracker <[EMAIL PROTECTED]>

[issue1709] logging: log actual function name

Changes by Vinay Sajip: -- status: pending -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1700] Regular Expression inline flags not handled correctly for some unicode characters

Fredrik Lundh added the comment: Looks like the wrong execution flags are being passed to the function that creates the actual pattern object; the SRE compiler does the right thing, but the engine isn't running with the right flags in the last case. Changing the call to _sre.compile in sre_compi

[issue1709] logging: log actual function name

umaxx added the comment: oops... i looked at python 2.4, not the latest trunk. my fault :( please close this issue. sorry for the noise... __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1719] Cosmetic patch for doc/code mismatch (msilib.UuidCreate)

Changes by Christian Heimes: -- assignee: -> georg.brandl nosy: +georg.brandl priority: -> low __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu