[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Committed the "%ls" fix with r67064. -- keywords: -needs review resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Christian Heimes <[EMAIL PROTECTED]> added the comment: I can't reproduce the problem with my installation of Cygwin on Windows XP. However the patch doesn't cause problems so you might apply it. -- nosy: +christian.heimes ___ Python tracker <[EMAIL P

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: 3.0rc1 builds and installs fine with the latest patch. Thanks! ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: The patch looks sound to me. Someone should probably test it under Cygwin. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: IIUC, another error return value (besides -1) is PATH_MAX, meaning that the buffer would overrun; correct me if I'm wrong. If I'm not, I propose that they get handles similarly. In addition, it might be safer to compare to (size_t)-1 (I keep

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Updated patch, which checks the return value of wcstombs. Added file: http://bugs.python.org/file11823/cygwin_badprintf-2.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I think cygwin_badprintf.patch needs to consider the case r==PATH_MAX; this happens when the conversion would need more than PATH_MAX bytes for the target buffer. In that case, I think it would be good enough to write "" into cfilename (using

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > I think this can be closed Well, after the proposed patch "cygwin_badprintf.patch" is reviewed and applied... ___ Python tracker <[EMAIL PROTECTED]>

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: > The IDLE problem is already corrected: see issue3628. In that case, then I think this can be closed; if I encounter any further issues after rc2, I'll open a new bug. Thank you for all your help. ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The IDLE problem is already corrected: see issue3628. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: 3.0rc1 together with the printf patch builds and installs. Some quick testing seems ok, but idle isn't working: $ idle3.0 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3.0/idlelib/run.py", line 76, i

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Since the bsddb module has been removed from py3k, the previous patch addresses the last issue for this ticket. ___ Python tracker <[EMAIL PROTECTED]> __

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: This patches corrects the bad printf, when the given filename is only 1-char long. -- keywords: +needs review Added file: http://bugs.python.org/file11534/cygwin_badprintf.patch ___ Python tr

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: Thank you for the patch; that allows the build to finish. The remaining issues are now: msg72029: printf("%ls",...) bug msg72044: does not build with db4.7 Finally proceeding to the install, now I get another error: mkdir ./Lib/plat

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: The mbstowcs problem should be fixed in r66187. What is the state of the other problems? Is this issue still a release blocker? -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]>

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: Another thing: _bsddb does not compile with db4.7: Modules/_bsddb.c: In function `DBSequence_get_cachesize': Modules/_bsddb.c:5022: warning: passing arg 2 of pointer to function from incompatible pointer type Modules/_bsddb.c: In funct

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: Thanks for your persistence with this. Corinna got _wcsrtombs_r fixed in newlib, so I imagine the next Cygwin 1.7 preview will have the fix. Unfortunately that won't help the still-stable Cygwin 1.5. I'm not sure what you mean by PyU

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: cygwin has also a nasty bug: printf("%ls", wide_string) fails for strings of length 1. %S has the same problem. $ ./python.exe ab ./python: can't open file 'ab': [Errno 2] No such file or directory $ ./python.exe a ./python The ou

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: See also issue3696, and the patch provided there. Yaakov, you should remove the _locale.dll from your build directory: for the compilation phase, better have no locale at all than a broken "U" as default encoding ("U" is the initial of

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: See also issue3626 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> added the comment: Thank you, that fixes that issue. But further along the build fails: Traceback (most recent call last): File "/usr/src/ports/python/python3.0/python3.0-3.0b3-1/src/Python-3.0b3/setup.py", line 1569, in class PyBuildInstallLib(i

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Cygwin seems to have a broken implementation of mbstowcs. See http://www.google.com/codesearch?q=cygwin+mbstowcs\(NULL The attached patch corrects the problem. -- keywords: +patch nosy: +amaury.forgeotdarc Added file: http://bu

[issue3626] python3.0 interpreter on Cygwin ignores all arguments

New submission from Yaakov (Cygwin Ports) <[EMAIL PROTECTED]>: Attempting to build 3.0b3, the sharedmods make target results only in a python command prompt. In fact, it seems that the interpreter doesn't accept any arguments: $ /usr/bin/python --version Python 2.5.2 $ /usr/bin/python -c 'prin